Solstice Enterprise Manager Reference Manual · 2550 Garcia Avenue Mountain View, CA 94043 U.S.A....

2550 Garcia AvenueMountain View, CA 94043U.S.A.

Solstice Enterprise ManagerReference Manual

Release 2.0

A Sun Microsystems, Inc. Business

PleaseRecycle

Copyright 1996 Sun Microsystems, Inc., 2550 Garcia Avenue, Mountain View, California 94043-1100 U.S.A. All rights reserved.

This product or document is protected by copyright and distributed under licenses restricting its use, copying, distribution, anddecompilation. No part of this product or document may be reproduced in any form by any means without prior writtenauthorization of Sun and its licensors, if any.

Portions of this product may be derived from the UNIX® system, licensed from Novell, Inc., and from the Berkeley 4.3 BSDsystem, licensed from the University of California. UNIX is a registered trademark in the United States and other countries and isexclusively licensed by X/Open Company Ltd. Third-party software, including font technology in this product, is protected bycopyright and licensed from Sun’s suppliers.

RESTRICTED RIGHTS: Use, duplication, or disclosure by the U.S. Government is subject to restrictions of FAR 52.227-14(g)(2)(6/87) and FAR 52.227-19(6/87), or DFAR 252.227-7015(b)(6/95) and DFAR 227.7202-1(a).

Sun, Sun Microsystems, the Sun logo, Solaris, SunSoft, Solstice, Solstice Emterprise Manager, SunNet manager, SunOS,OpenWindows, DeskSet, ONC, SNM, and NFS are trademarks or registered trademarks of Sun Microsystems, Inc. in the UnitedStates and other countries. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARCInternational, Inc. in the United States and other countries. Products bearing SPARC trademarks are based upon an architecturedeveloped by Sun Microsystems, Inc.

The OPEN LOOK® and Sun™ Graphical User Interfaces were developed by Sun Microsystems, Inc. for its users and licensees.Sun acknowledges the pioneering efforts of Xerox in researching and developing the concept of visual or graphical userinterfaces for the computer industry. Sun holds a non-exclusive license from Xerox to the Xerox Graphical User Interface, whichlicense also covers Sun’s licensees who implement OPEN LOOK GUIs and otherwise comply with Sun’s written licenseagreements.

X Window System is a product of the X Consortium, Inc.

THIS PUBLICATION IS PROVIDED “AS IS” WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED,INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR APARTICULAR PURPOSE, OR NON-INFRINGEMENT.

iii

Contents

Preface. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxxv

1. Enterprise Manager Overview . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1

1.1 Solstice EM Features and Functions. . . . . . . . . . . . . . . . . . 1-1

1.2 Solstice EM High-Level Components . . . . . . . . . . . . . . . . 1-2

1.3 Solstice EM Management Information Server (MIS) . . . . 1-3

1.3.1 Access to Data in the MIS. . . . . . . . . . . . . . . . . . . . . . 1-4

1.3.2 Object Orientation. . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5

1.3.3 ASN.1 Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6

1.3.4 Transparent Access to the Distributed Storageof Managed Objects . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6

1.4 Solstice EM Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-7

1.5 Solstice EM Application Programming Interface (API). . 1-9

1.5.1 API Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-10

1.5.2 Application Development Support Tools. . . . . . . . . 1-11

2. Management Information Server (MIS) . . . . . . . . . . . . . . . . . . 2-1

2.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1

iv Solstice Enterprise Manager Reference Manual

2.2 MIS Subcomponents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3

2.2.1 Portable Management Interface (PMI) . . . . . . . . . . . 2-3

2.2.2 Management Information Tree (MIT) . . . . . . . . . . . . 2-4

2.2.3 MetaData Repository (MDR) . . . . . . . . . . . . . . . . . . . 2-4

2.2.4 Nerve Center . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4

2.2.5 CMIP Management Protocol Adaptor . . . . . . . . . . . 2-4

2.2.6 SNMP Protocol Driver Module . . . . . . . . . . . . . . . . . 2-5

2.2.7 RPC Protocol Driver Module. . . . . . . . . . . . . . . . . . . 2-5

2.2.8 Alarm Service Module . . . . . . . . . . . . . . . . . . . . . . . . 2-5

2.2.9 Persistent Storage . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-5

2.2.10 em_login Daemon. . . . . . . . . . . . . . . . . . . . . . . . . . . 2-5

2.2.11 em_mis Daemon . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-6

2.2.12 em_snmp-trap Daemon . . . . . . . . . . . . . . . . . . . . . . 2-6

2.2.13 em_ncam Daemon . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-6

2.2.14 em_snmfwd Daemon . . . . . . . . . . . . . . . . . . . . . . . . . 2-6

2.2.15 em_nnmpa Daemon. . . . . . . . . . . . . . . . . . . . . . . . . . . 2-7

2.2.16 em_cmip Daemon . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-7

2.2.17 em_autod Daemon. . . . . . . . . . . . . . . . . . . . . . . . . . . 2-7

2.2.18 em_datad Daemon. . . . . . . . . . . . . . . . . . . . . . . . . . . 2-7

2.2.19 em_log2rdb. <database_name> Daemon . . . . . . . . . 2-7

2.3 Starting the Solstice EM MIS . . . . . . . . . . . . . . . . . . . . . . . . 2-8

2.3.1 Starting the Solstice EM MIS and Preservingthe Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-9

2.3.2 Starting the Solstice EM MIS withoutPreserving the Data. . . . . . . . . . . . . . . . . . . . . . . . . . . 2-9

Contents v

2.3.3 Starting the Solstice EM MIS and Reinitializingthe Configuration Data. . . . . . . . . . . . . . . . . . . . . . . . 2-11

2.3.4 Starting the Solstice EM Applications . . . . . . . . . . . 2-12

2.4 Terminating the Solstice EM MIS . . . . . . . . . . . . . . . . . . . . 2-13

2.5 Starting the CMIP MPA Daemon . . . . . . . . . . . . . . . . . . . . 2-13

2.6 Backing Up and Restoring the Runtime Database . . . . . . 2-14

2.7 How to Run the MIS as Non-Root . . . . . . . . . . . . . . . . . . . 2-14

3. Compilers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1

3.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1

3.1.1 Management Information Tree (MIT) . . . . . . . . . . . . 3-2

3.1.2 Object Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2

3.1.3 Adding a New Managed Object to the MDR. . . . . . 3-3

3.2 The ASN.1 Compiler . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4

3.2.1 ASN.1 Documents. . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4

3.2.2 Compiling ASN.1 Documents . . . . . . . . . . . . . . . . . . 3-5

3.2.3 See Also . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5

3.3 The GDMO Compiler. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-6

3.3.1 GDMO Compiler Input . . . . . . . . . . . . . . . . . . . . . . . 3-6

3.3.2 Managing Related GDMO Documents. . . . . . . . . . . 3-7

3.3.3 GDMO Compiler Output . . . . . . . . . . . . . . . . . . . . . . 3-7

3.3.4 em_gdmo Command Line Syntax . . . . . . . . . . . . . . . 3-8

3.4 The Concise MIB Compiler . . . . . . . . . . . . . . . . . . . . . . . . . 3-10

3.4.1 Names of Input and Output Files . . . . . . . . . . . . . . . 3-12

3.4.2 em_cmib2gdmo Command Line Syntax . . . . . . . . . 3-13

vi Solstice Enterprise Manager Reference Manual

3.4.3 See Also . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-14

3.4.4 Diagnostics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-15

3.5 The Schema Compiler . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-15

3.5.1 em_snm2gdmo Command Line Syntax . . . . . . . . . . 3-15

3.5.2 See Also . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-17

3.5.3 Diagnostics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-17

4. Management Protocol Support . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1

4.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1

4.1.1 Management Protocol Adaptor Overview . . . . . . . 4-1

4.1.2 Protocol Driver Module Overview . . . . . . . . . . . . . . 4-2

4.1.3 SNMP Version 2 Support . . . . . . . . . . . . . . . . . . . . . . 4-2

4.2 CMIP MPA. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2

4.2.1 Starting a CMIP MPA . . . . . . . . . . . . . . . . . . . . . . . . . 4-3

4.2.2 Configuring a CMIP MPA . . . . . . . . . . . . . . . . . . . . . 4-4

4.2.3 CMIP MPA and MIS Messages . . . . . . . . . . . . . . . . . 4-4

4.3 Proprietary Protocol MPA . . . . . . . . . . . . . . . . . . . . . . . . . . 4-8

4.4 SNMP PDM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-9

4.5 RPC PDM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-9

5. Log Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1

5.1 MIS Logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2

5.1.1 MIS Logging Services Provided . . . . . . . . . . . . . . . . 5-2

5.1.2 Alarm Logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-4

5.2 Historical Logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-6

5.2.1 Enabling Historical Logging . . . . . . . . . . . . . . . . . . . 5-6

Contents vii

5.2.2 Historical Log File Format . . . . . . . . . . . . . . . . . . . . . 5-7

5.3 Historical Relational Database (RDB) Logging. . . . . . . . . 5-8

5.3.1 Configuration File . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-9

5.3.2 Database Schema Definition File. . . . . . . . . . . . . . . . 5-10

5.3.3 Starting the em_log2rdb Daemon. . . . . . . . . . . . . . 5-25

5.4 Miscellaneous Processing of Database Records . . . . . . . . 5-26

5.4.1 Starting Two em_log2rdb Daemons andLogging the Records to Two Databases . . . . . . . . . . 5-26

5.4.2 Storing Different Types of emAlarmRecord inDifferent Databases. . . . . . . . . . . . . . . . . . . . . . . . . . . 5-27

5.4.3 Report Generation. . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-27

6. Alarm Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1

6.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1

6.2 Alarm Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2

6.3 The Alarm Service in Action . . . . . . . . . . . . . . . . . . . . . . . . 6-6

6.4 Configuring the Alarm Service . . . . . . . . . . . . . . . . . . . . . . 6-9

6.4.1 Adding Log Objects to emAlarmLogList . . . . . . . . . 6-9

6.4.2 Deleting Log Objects from emAlarmLogList. . . . . . 6-10

6.4.3 Turning Off the Alarm Service . . . . . . . . . . . . . . . . . 6-10

6.5 Alarm Information Display in EM Applications . . . . . . . 6-10

6.5.1 Alarm Information Display in Alarm Manager . . . 6-10

6.5.2 Alarm Information Display in Viewer . . . . . . . . . . . 6-11

6.6 User-configurable Alarm Log Record Filter forAlarm Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-12

7. MIS to MIS Communication. . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1

viii Solstice Enterprise Manager Reference Manual

7.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1

7.1.1 MIS-MIS Communication . . . . . . . . . . . . . . . . . . . . . 7-1

7.1.2 Event Forwarding Discriminators (EFDs) . . . . . . . . 7-8

7.2 Using MIS Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-9

7.2.1 Starting the MIS Manager . . . . . . . . . . . . . . . . . . . . . 7-9

7.2.2 Using MIS Manager Windows and Menus . . . . . . . 7-10

7.3 Configuring MIS-to-MIS Communication. . . . . . . . . . . . . 7-15

7.3.1 Connecting to a Remote MIS . . . . . . . . . . . . . . . . . . . 7-15

7.4 Logging Events Sent from Another MIS . . . . . . . . . . . . . . 7-16

8. Application Launcher. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-1

8.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-1

8.2 Starting the Application Launcher . . . . . . . . . . . . . . . . . . . 8-1

8.3 Using the Application Launcher Windows,Icons, and Menus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-2

8.3.1 File Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-4

8.4 Adding, Modifying, and Deleting Icons . . . . . . . . . . . . . . 8-10

8.4.1 Adding an Application to theApplication Launcher . . . . . . . . . . . . . . . . . . . . . . . . . 8-10

8.4.2 Modifying the Launching Configurationfor an Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-11

8.4.3 Deleting an Application from theApplication Launcher . . . . . . . . . . . . . . . . . . . . . . . . . 8-12

9. Access Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-1

9.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-1

9.1.1 User Levels. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-2

9.1.2 Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-2

Contents ix

9.2 Enabling and Disabling Access Control . . . . . . . . . . . . . . 9-3

9.3 Granting Super User and Trusted Host Access . . . . . . . . 9-4

9.4 Starting the Access Manager . . . . . . . . . . . . . . . . . . . . . . . . 9-6

9.4.1 Starting the Access Manager from theApplication Launcher . . . . . . . . . . . . . . . . . . . . . . . . . 9-6

9.4.2 Starting the Access Manager From theCommand Line . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-7

9.5 Using Access Manager Windows and Menus. . . . . . . . . . 9-8

9.5.1 The File Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-9

9.5.2 The Object Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-18

9.5.3 The View Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-32

10. Viewer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-1

10.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-1

10.1.1 Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-2

10.1.2 Views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-3

10.2 Starting the Viewer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-5

10.2.1 Starting the Viewer from the ApplicationLauncher . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-5

10.2.2 Starting the Viewer From the Command Line. . . . . 10-6

10.3 Using the Viewer Windows and Menus . . . . . . . . . . . . . . 10-7

10.3.1 Using the Main Window Toolbar . . . . . . . . . . . . . . . 10-11

10.3.2 Using Object Icons . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-13

10.3.3 Using the Object Icon Menus. . . . . . . . . . . . . . . . . . . 10-14

10.3.4 File Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-15

10.3.5 Object Menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-15

x Solstice Enterprise Manager Reference Manual

10.3.6 Edit Menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-17

10.3.7 View Menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-19

10.3.8 Tools Menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-41

10.4 Summary of Common Viewer Tasks . . . . . . . . . . . . . . . . . 10-59

10.4.1 Populating the Viewer . . . . . . . . . . . . . . . . . . . . . . . . 10-59

10.4.2 Creating a Viewer Icon . . . . . . . . . . . . . . . . . . . . . . . . 10-60

10.4.3 Configuring a Viewer Icon (Device,Link, Container, or Multimonitor) . . . . . . . . . . . . . . 10-60

10.4.4 Performing a Get or Set Request . . . . . . . . . . . . . . . . 10-60

10.4.5 Checking on the Alarms for a Managed Object . . . 10-61

10.4.6 Clearing Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-61

10.4.7 Propagating Alarm Severity to Parent Views . . . . . 10-61

10.4.8 Displaying and Selecting an ObjectLocated in the Current View . . . . . . . . . . . . . . . . . . . 10-61

10.4.9 Switching Views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-62

10.4.10 Searching Multiple Views for an Object . . . . . . . . . . 10-62

10.4.11 Changing the View Navigator Orientation . . . . . . . 10-62

10.4.12 Zooming In or Out . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-62

10.4.13 Toggling the Display of an Object Typein a View. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-63

10.4.14 Adding an Object to the Viewer’sObject Palette . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-63

10.4.15 Adding New Geographical Maps forthe Viewer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-65

10.5 The Viewer Configuration File . . . . . . . . . . . . . . . . . . . . . . 10-67

10.5.1 File Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-68

Contents xi

11. Discover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-1

11.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-1

11.1.1 The Discover Function . . . . . . . . . . . . . . . . . . . . . . . . 11-1

11.1.2 The Monitor Function. . . . . . . . . . . . . . . . . . . . . . . . . 11-2

11.2 Starting Discover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-2

11.2.1 Discover Main Window . . . . . . . . . . . . . . . . . . . . . . . 11-2

11.2.2 How Discover Works . . . . . . . . . . . . . . . . . . . . . . . . . 11-5

11.2.3 Discover and Network Security . . . . . . . . . . . . . . . . 11-7

11.3 Discover Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-7

11.3.1 ICMP/SNMP Field . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-9

11.3.2 Objects Field . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-11

11.3.3 General Field . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-12

11.3.4 Gateways . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-14

11.3.5 Agent Mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-14

11.4 Monitor Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-15

11.4.1 Objects to Monitor. . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-17

11.4.2 General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-17

11.4.3 Log Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-18

11.4.4 Timers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-19

11.5 Running Discover From the Command Line . . . . . . . . . . 11-20

11.5.1 Monitor Command Line Options . . . . . . . . . . . . . . . 11-23

11.5.2 Debugging Options. . . . . . . . . . . . . . . . . . . . . . . . . . . 11-24

12. Data Collector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-1

12.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-1

xii Solstice Enterprise Manager Reference Manual

12.1.1 Request Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-1

12.1.2 The Data Collector Daemon (em_datad ). . . . . . . . . 12-2

12.2 Starting the Data Collector . . . . . . . . . . . . . . . . . . . . . . . . . 12-3

12.2.1 Starting the Data Collector from theApplication Launcher . . . . . . . . . . . . . . . . . . . . . . . . . 12-3

12.2.2 Starting the Data Collector From theCommand Line . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-3

12.3 Using Data Collector Windows and Menus . . . . . . . . . . . 12-4

12.3.1 File Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-5

12.3.2 Object Menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-5

12.4 Data Collector GDMO Classes . . . . . . . . . . . . . . . . . . . . . . 12-14

12.4.1 The dataCollector GDMO class . . . . . . . . . . . . . . . . . 12-14

12.4.2 The dataCollectorEntry Object GDMO Class . . . . . 12-15

13. Log Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-1

13.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-1

13.1.1 Attributes of a Log . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-2

13.1.2 Log Records Generated by RequestDesigner Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-3

13.2 Using the Log Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-4

13.2.1 Starting the Log Manager. . . . . . . . . . . . . . . . . . . . . . 13-4

13.2.2 View Menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-12

13.2.3 Tools Menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-14

13.3 Defining the Discriminator Construct . . . . . . . . . . . . . . . . 13-15

13.3.1 Discriminator that Accepts Notificationsof a Specific Type. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-17

13.3.2 Discriminator Construct with Multiple ANDs . . . . 13-18

Contents xiii

13.3.3 A Discriminator Construct that AcceptsAll Notifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-19

13.3.4 A Discriminator that Accepts No Notifications . . . 13-19

13.4 Sample Discriminator Constructs. . . . . . . . . . . . . . . . . . . . 13-20

13.4.1 Creation of an Object Instance. . . . . . . . . . . . . . . . . . 13-20

13.4.2 Deletion of An Object Instance . . . . . . . . . . . . . . . . . 13-20

13.4.3 Attribute Value Change of an Object Instance. . . . . 13-21

13.4.4 State Changes Received From Agent . . . . . . . . . . . . 13-22

13.4.5 Default Discriminator. . . . . . . . . . . . . . . . . . . . . . . . . 13-22

13.5 Log Manager Configuration File . . . . . . . . . . . . . . . . . . . . 13-23

14. Log Viewer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-1

14.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-1

14.2 Starting the Log Viewer . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-1

14.3 The Log Viewer Main Window. . . . . . . . . . . . . . . . . . . . . . 14-3

14.3.1 Record Details Button. . . . . . . . . . . . . . . . . . . . . . . . . 14-4

14.3.2 File Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-6

14.3.3 Object Menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-7

14.3.4 View Menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-8

14.3.5 Tools Menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-11

14.4 Using the Log Viewer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-11

14.4.1 Viewing a Detailed Log Record. . . . . . . . . . . . . . . . . 14-12

14.4.2 Choosing Which Log Records to Display . . . . . . . . 14-12

14.4.3 Searching For a Log Record . . . . . . . . . . . . . . . . . . . . 14-13

14.4.4 Deleting a Log Record From the MIS . . . . . . . . . . . . 14-14

xiv Solstice Enterprise Manager Reference Manual

14.4.5 Modifying the Log Record Views . . . . . . . . . . . . . . . 14-14

14.4.6 Adding Other Tools to the Tool Menu . . . . . . . . . . . 14-19

14.4.7 Starting the Log Manager from the Log Viewer . . . 14-21

14.5 Log Viewer Configuration File . . . . . . . . . . . . . . . . . . . . . . 14-21

15. Alarm Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-1

15.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-1

15.2 Starting the Alarm Manager . . . . . . . . . . . . . . . . . . . . . . . . 15-1

15.3 Using the Alarm Manager . . . . . . . . . . . . . . . . . . . . . . . . . . 15-3

15.3.1 Alarm Associations Window . . . . . . . . . . . . . . . . . . . 15-4

15.3.2 Alarm Instances Window. . . . . . . . . . . . . . . . . . . . . . 15-6

15.3.3 Alarm Details Window. . . . . . . . . . . . . . . . . . . . . . . . 15-8

15.3.4 Configuring Alarm Manager . . . . . . . . . . . . . . . . . . . 15-9

15.3.5 Alarm States. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-10

15.4 Alarm Manager Menu Bar. . . . . . . . . . . . . . . . . . . . . . . . . . 15-11

15.4.1 File Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-11

15.4.2 Object Menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-16

15.4.3 Edit Menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-17

15.4.4 View Menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-18

15.4.5 View Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-23

15.4.6 Tools Menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-28

15.5 Alarm States . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-30

15.6 Alarm Associations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-31

15.7 Alarm Manager Default Properties . . . . . . . . . . . . . . . . . . 15-32

15.7.1 View Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-32

Contents xv

15.7.2 Association Properties . . . . . . . . . . . . . . . . . . . . . . . . 15-33

15.7.3 Filter Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-33

15.8 Alarm Manager Configuration Files . . . . . . . . . . . . . . . . . 15-33

15.8.1 Configuration File Formats . . . . . . . . . . . . . . . . . . . . 15-34

16. SNMP Browser . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-1

16.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-1

16.2 Browsing MIB Information . . . . . . . . . . . . . . . . . . . . . . . . . 16-2

16.3 Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-2

16.4 Starting the SNMP Browser . . . . . . . . . . . . . . . . . . . . . . . . 16-3

16.4.1 Starting the SNMP Browser from theApplication Launcher . . . . . . . . . . . . . . . . . . . . . . . . . 16-3

16.4.2 Starting the SNMP Browser from the Viewer. . . . . 16-4

16.4.3 Starting the SNMP Browser from theCommand Line . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-5

16.5 Using the SNMP Browser Windows and Menus . . . . . . . 16-6

16.5.1 File Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-10

16.5.2 View Menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-20

16.6 Summary of Basic SNMP Browser Tasks. . . . . . . . . . . . . . 16-21

16.6.1 Viewing Basic MIB Information in theMain Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-21

16.6.2 Selecting a New Default Agent . . . . . . . . . . . . . . . . . 16-21

16.6.3 Creating New Tables. . . . . . . . . . . . . . . . . . . . . . . . . . 16-22

16.6.4 Making Selections in Tables . . . . . . . . . . . . . . . . . . . . 16-22

16.6.5 Adding New Items to a Table . . . . . . . . . . . . . . . . . . 16-22

16.6.6 Adding and Creating New Entries in a Table . . . . . 16-23

xvi Solstice Enterprise Manager Reference Manual

16.6.7 Rearranging Table Contents. . . . . . . . . . . . . . . . . . . . 16-24

16.6.8 Deleting Table Contents . . . . . . . . . . . . . . . . . . . . . . . 16-24

16.6.9 Adding Agents to a Table. . . . . . . . . . . . . . . . . . . . . . 16-24

16.6.10 Getting MIB Attribute Data . . . . . . . . . . . . . . . . . . . . 16-25

16.6.11 Setting MIB Attribute Data . . . . . . . . . . . . . . . . . . . . 16-25

16.6.12 Polling. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-25

17. Data Viewer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-1

17.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-1

17.2 Starting the Data Viewer . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-2

17.2.1 Starting the Data Viewer from theCommand Line . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-2

17.2.2 Starting the Data Viewer from theViewer Application . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-3

17.3 Using the Data Viewer Windows and Menus . . . . . . . . . . 17-4

17.3.1 The Polling Window . . . . . . . . . . . . . . . . . . . . . . . . . . 17-6

18. Grapher. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-1

18.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-1

18.2 Starting the Grapher. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-2

18.2.1 Starting the Grapher from the Command Line . . . . 18-2

18.2.2 Starting the Grapher from the Alarm Manager. . . . 18-2

18.3 Using the Grapher Windows and Menus . . . . . . . . . . . . . 18-4

18.3.1 Graph Selection List . . . . . . . . . . . . . . . . . . . . . . . . . . 18-5

18.3.2 File Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-6

18.3.3 Object Menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-8

18.3.4 Edit Menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-16

Contents xvii

18.4 Summary of Basic Grapher Tasks . . . . . . . . . . . . . . . . . . . . 18-16

18.4.1 Displaying Data Graphs. . . . . . . . . . . . . . . . . . . . . . . 18-16

18.4.2 Zooming, Scaling, and ResettingGraph Displays . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-16

19. Object Configuration Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-1

19.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-1

19.2 Starting the Object Configuration Tool . . . . . . . . . . . . . . . 19-2

19.3 Using the Object Configuration Tool . . . . . . . . . . . . . . . . . 19-4

19.3.1 Name Field. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-6

19.3.2 Type Field. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-7

19.3.3 Object Description. . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-7

19.3.4 Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-10

19.3.5 Display Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-21

19.3.6 Coordinates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-21

20. Object Editor/Browser . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-1

20.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-1

20.2 Starting OBED. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-2

20.3 OBED’s Main Window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-4

20.3.1 MIT Navigator. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-5

20.3.2 Path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-5

20.4 File Menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-6

20.4.1 Properties... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-6

20.4.2 Exit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-8

20.5 Object Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-8

xviii Solstice Enterprise Manager Reference Manual

20.5.1 Get... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-9

20.5.2 Action . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-11

20.5.3 Create.... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-13

20.5.4 Delete . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-15

20.5.5 Deselect . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-15

20.6 Object Configuration Window . . . . . . . . . . . . . . . . . . . . . . 20-15

20.6.1 Buttons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-18

20.7 Using the Object Editor to Access the Objectsin a CMIP Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-19

21. Topology Import/Export Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-1

21.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-1

21.2 Starting the Topology Import/Export Tool . . . . . . . . . . . . 21-2

21.3 Using the Topology Import/Export Tool. . . . . . . . . . . . . . 21-4

21.3.1 Exported Information . . . . . . . . . . . . . . . . . . . . . . . . . 21-4

21.3.2 Not Exported Information . . . . . . . . . . . . . . . . . . . . . 21-5

22. Automatic Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-1

22.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-1

22.2 Default autoManagementEntry Objects . . . . . . . . . . . . . . 22-2

22.3 Creating autoManagementEntry Objects . . . . . . . . . . . . . 22-3

22.4 Using OBED to Start/Stop Automatic Management . . . . 22-6

22.5 Automatic Management Daemon (em_autod ) . . . . . . . . 22-7

23. Command Line Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-1

23.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-1

23.2 Command Line Options . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-2

Contents xix

23.2.1 em Command. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-2

23.2.2 em_accesscmd Command . . . . . . . . . . . . . . . . . . . . 23-2

23.2.3 em_accessmgr Command . . . . . . . . . . . . . . . . . . . . 23-5

23.2.4 em_alarmmgr Command . . . . . . . . . . . . . . . . . . . . . 23-6

23.2.5 em_asn1 Command . . . . . . . . . . . . . . . . . . . . . . . . . . 23-7

23.2.6 em_autod Daemon. . . . . . . . . . . . . . . . . . . . . . . . . . . 23-7

23.2.7 em_cmib2gdmo Command . . . . . . . . . . . . . . . . . . . . 23-8

23.2.8 em_cmip Daemon . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-9

23.2.9 em_compose_all Command . . . . . . . . . . . . . . . . . . 23-9

23.2.10 em_compose_oc Command . . . . . . . . . . . . . . . . . . . 23-10

23.2.11 em_compose_poc Command . . . . . . . . . . . . . . . . . . 23-10

23.2.12 em_datacollector Command. . . . . . . . . . . . . . . . 23-11

23.2.13 em_datad Daemon. . . . . . . . . . . . . . . . . . . . . . . . . . . 23-11

23.2.14 em_dataviewer Command . . . . . . . . . . . . . . . . . . . 23-12

23.2.15 em_debug Command . . . . . . . . . . . . . . . . . . . . . . . . . 23-13

23.2.16 em_discover Command . . . . . . . . . . . . . . . . . . . . . 23-16

23.2.17 em_gdmo Command . . . . . . . . . . . . . . . . . . . . . . . . . . 23-20

23.2.18 em_grapher Command . . . . . . . . . . . . . . . . . . . . . . 23-21

23.2.19 em_help Command . . . . . . . . . . . . . . . . . . . . . . . . . . 23-21

23.2.20 em_imex Command . . . . . . . . . . . . . . . . . . . . . . . . . . 23-22

23.2.21 em_load_name_bindings Command . . . . . . . . . . 23-22

23.2.22 em_load_nc_templates Command . . . . . . . . . . . 23-23

23.2.23 em_log2rdb.< database> Daemon . . . . . . . . . . . . . . 23-23

23.2.24 em_login Daemon. . . . . . . . . . . . . . . . . . . . . . . . . . . 23-24

xx Solstice Enterprise Manager Reference Manual

23.2.25 em_logmgr Command. . . . . . . . . . . . . . . . . . . . . . . . 23-24

23.2.26 em_logview Command . . . . . . . . . . . . . . . . . . . . . . 23-25

23.2.27 em_mismgr Command. . . . . . . . . . . . . . . . . . . . . . . . 23-26

23.2.28 em_ncam Daemon . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-27

23.2.29 em_ncexport Command . . . . . . . . . . . . . . . . . . . . . 23-27

23.2.30 em_ncimport Command . . . . . . . . . . . . . . . . . . . . . 23-28

23.2.31 em_nnadd Command . . . . . . . . . . . . . . . . . . . . . . . . . 23-29

23.2.32 em_nnconfig Command . . . . . . . . . . . . . . . . . . . . . 23-30

23.2.33 em_nnmpa Command . . . . . . . . . . . . . . . . . . . . . . . . . 23-31

23.2.34 em_obcodegen Command . . . . . . . . . . . . . . . . . . . . 23-32

23.2.35 em_obed Command . . . . . . . . . . . . . . . . . . . . . . . . . . 23-33

23.2.36 em_objop Command . . . . . . . . . . . . . . . . . . . . . . . . . 23-33

23.2.37 em_oct Command . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-34

23.2.38 em_reqedit Command . . . . . . . . . . . . . . . . . . . . . . 23-35

23.2.39 em_services Command . . . . . . . . . . . . . . . . . . . . . 23-35

23.2.40 em_snm_type_import Command . . . . . . . . . . . . . 23-36

23.2.41 em_snmdb_import Command. . . . . . . . . . . . . . . . . 23-37

23.2.42 em_snm2gdmo Command . . . . . . . . . . . . . . . . . . . . . 23-37

23.2.43 em_snmfwd Daemon . . . . . . . . . . . . . . . . . . . . . . . . . 23-38

23.2.44 em_snmpbrowser Command . . . . . . . . . . . . . . . . . . 23-39

23.2.45 em_topoimex Command . . . . . . . . . . . . . . . . . . . . . 23-39

23.2.46 em_viewer Command. . . . . . . . . . . . . . . . . . . . . . . . 23-41

A. Standard Event Notifications . . . . . . . . . . . . . . . . . . . . . . . . . . . A-1

B. Environment Variables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-1

Contents xxi

C. Enterprise Manager File Structure . . . . . . . . . . . . . . . . . . . . . . . C-1

D. CMIS Scoping and Filtering . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-1

D.1 OSI Definition of Scoping and Filtering. . . . . . . . . . . . . . . D-1

D.2 Enterprise Manager Implementation . . . . . . . . . . . . . . . . . D-6

D.2.1 Log Manager Discriminator Construct. . . . . . . . . . . D-6

D.2.2 Filtering as an Aspect of Album Derivation . . . . . . D-7

E. Additional Sources of Information . . . . . . . . . . . . . . . . . . . . . . E-1

E.1 Network Management Concepts . . . . . . . . . . . . . . . . . . . . E-1

E.2 ISO Network Management Concepts . . . . . . . . . . . . . . . . E-2

E.2.1 General Concepts . . . . . . . . . . . . . . . . . . . . . . . . . . . . E-2

E.2.2 Abstract Syntax Notation One (ASN.1) . . . . . . . . . . E-3

E.2.3 CMIP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E-3

E.2.4 CMIP over TCP/IP . . . . . . . . . . . . . . . . . . . . . . . . . . . E-3

E.2.5 GDMO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E-3

E.2.6 ACSE. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E-4

E.2.7 ROSE. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E-4

E.2.8 Directory Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E-4

E.2.9 CMIS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E-4

E.2.10 Management Information Model . . . . . . . . . . . . . . . E-4

E.2.11 System Management. . . . . . . . . . . . . . . . . . . . . . . . . . E-5

E.2.12 Logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E-6

E.2.13 Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E-6

E.3 Telecommunication Management Network(TMN) Standards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E-7

xxii Solstice Enterprise Manager Reference Manual

E.4 Internet Network Management Concepts . . . . . . . . . . . . . E-7

E.4.1 SNMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E-7

E.4.2 SNMP Version 1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E-7

E.4.3 SNMP Version 2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E-7

E.4.4 ISO and Internet Management Co-existence . . . . . . E-8

E.4.5 MIB I . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E-9

E.4.6 MIB II . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E-9

E.4.7 Host Resources MIB . . . . . . . . . . . . . . . . . . . . . . . . . . E-9

E.5 Application-to-Application Communication . . . . . . . . . . E-10

E.6 Additional Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . E-10

E.7 Where to Find These Reference Materials . . . . . . . . . . . . . E-10

E.7.1 ISO Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . E-10

E.7.2 Internet RFCs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E-11

E.7.3 OMNIPoint Specifications . . . . . . . . . . . . . . . . . . . . . E-11

Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Glossary-1

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Index-1

xxiii

Figures

Figure 1-1 EM High-Level Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2

Figure 3-1 The Concise MIB Compiler in Context. . . . . . . . . . . . . . . . . . . . 3-12

Figure 5-1 Log Management Process. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2

Figure 5-2 Historical RDB Logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-8

Figure 5-3 Entity Relationship Model for Log Record Database. . . . . . . . 5-16

Figure 6-1 Logging nerveCenterAlarms, CMIP notifications, andinternetAlarms to the AlarmLog. . . . . . . . . . . . . . . . . . . . . . . . . 6-4

Figure 6-2 Logging snmAlarmTraps to the AlarmLog. . . . . . . . . . . . . . . . 6-5

Figure 6-3 Alarm Service and Components . . . . . . . . . . . . . . . . . . . . . . . . . 6-6

Figure 7-1 MITs of Two Unconnected MISs . . . . . . . . . . . . . . . . . . . . . . . . . 7-4

Figure 7-2 MITs of Two Connected MISs . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-5

Figure 7-3 MIS-MIS Connection Over Three Networks . . . . . . . . . . . . . . . 7-6

Figure 7-4 Local and Non-local Objects as Seen from MIS B1 . . . . . . . . . . 7-7

Figure 7-5 Local and Non-local Objects as Seen from MIS net1 . . . . . . . . 7-7

Figure 7-6 Objects Seen from MIS net3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-8

Figure 7-7 MIS Manager Main Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-11

Figure 7-8 MIS Manager Advanced Settings Window . . . . . . . . . . . . . . . . 7-13

xxiv Solstice Enterprise Manager Reference Manual

Figure 8-1 Application Launcher Main Window. . . . . . . . . . . . . . . . . . . . . 8-3

Figure 8-2 Configure Applications Window . . . . . . . . . . . . . . . . . . . . . . . . 8-5

Figure 8-3 Select File Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-8

Figure 9-1 Access Manager Main Window. . . . . . . . . . . . . . . . . . . . . . . . . . 9-8

Figure 9-2 Export Customized Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-10

Figure 9-3 Export to File Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-11

Figure 9-4 Import from File Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-13

Figure 9-5 Print Window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-15

Figure 9-6 File Selection Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-16

Figure 9-7 Create Group Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-19

Figure 9-8 Create Group Window with Open Folders . . . . . . . . . . . . . . . . 9-21

Figure 9-9 Group Properties Window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-24

Figure 9-10 Duplicate Group Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-25

Figure 9-11 Create User Window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-27

Figure 9-12 User Properties Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-29

Figure 9-13 Duplicate User Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-31

Figure 9-14 The Find Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-33

Figure 9-15 User Privileges Window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-34

Figure 10-1 Topology and Non-Topology Views . . . . . . . . . . . . . . . . . . . . . 10-4

Figure 10-2 Viewer Main Window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-7

Figure 10-3 Multiple Views Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-9

Figure 10-4 Viewer Main Window Toolbar . . . . . . . . . . . . . . . . . . . . . . . . . . 10-11

Figure 10-5 Object Configuration Window. . . . . . . . . . . . . . . . . . . . . . . . . . . 10-16

Figure 10-6 View Properties Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-20

Figure 10-7 Variable Icon Size Setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-24

Figures xxv

Figure 10-8 Color Chooser Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-27

Figure 10-9 Background Properties Window. . . . . . . . . . . . . . . . . . . . . . . . . 10-31


Figure 10-11 Layers Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-35

Figure 10-12 Map Layers Window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-36

Figure 10-13 Layout Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-38

Figure 10-14 Configure Tools Window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-42

Figure 10-15 Configure Device Options Window . . . . . . . . . . . . . . . . . . . . . . 10-46

Figure 10-16 Default Activations Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-49

Figure 10-17 Find Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-51

Figure 10-18 Find: Add to Window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-53

Figure 10-19 Requests Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-54

Figure 10-20 Object Palette Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-56

Figure 10-21 View List Window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-57

Figure 11-1 Discover Main Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-3

Figure 11-2 Discover Properties Window. . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-8

Figure 11-3 Monitor Properties Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-16

Figure 12-1 Data Collector Main Window . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-4

Figure 12-2 Create Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-6

Figure 12-3 Object Browser Window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-8

Figure 12-4 Attribute List Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-10

Figure 13-1 Log Manager Main Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-6

Figure 13-2 Properties Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-7


Figure 13-4 Log Object Window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-10

xxvi Solstice Enterprise Manager Reference Manual


Figure 13-6 Label Names Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-13

Figure 14-1 Log Viewer Main Window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-3

Figure 14-2 Record Details Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-5


Figure 14-4 Log Filter Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-9

Figure 14-5 Log Filter Pull-down Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-10


Figure 14-7 Find Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-13


Figure 14-9 Sort Order Window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-17


Figure 15-1 Alarm Manager Summary Window . . . . . . . . . . . . . . . . . . . . . . 15-3

Figure 15-2 Association Properties Window . . . . . . . . . . . . . . . . . . . . . . . . . 15-5

Figure 15-3 Alarm Associations Window. . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-6

Figure 15-4 Alarm Manager Instances Window . . . . . . . . . . . . . . . . . . . . . . 15-7

Figure 15-5 Alarm Details Window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-8



Figure 15-8 Log Properties Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-14


Figure 15-10 Display Text Tool Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-16

Figure 15-11 Alarm Filter Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-19

Figure 15-12 Pulldown Filter List. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-20

Figure 15-13 Association Properties Window . . . . . . . . . . . . . . . . . . . . . . . . . 15-21

Figures xxvii

Figure 15-14 View Properties window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-23

Figure 15-15 Label Names Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-25

Figure 15-16 Sort Order Window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-27


Figure 15-18 Graph Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-29

Figure 16-1 SNMP Browser Main Window . . . . . . . . . . . . . . . . . . . . . . . . . . 16-6

Figure 16-2 SNMP Browser Main Window Example . . . . . . . . . . . . . . . . . . 16-7

Figure 16-3 Table Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-11


Figure 16-5 File Selection Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-14

Figure 16-6 Add Agent window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-17

Figure 16-7 Poll Setup Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-19

Figure 17-1 Data Viewer Main Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-4

Figure 17-2 Polling Window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-6

Figure 18-1 Alarm Manager Graph Window . . . . . . . . . . . . . . . . . . . . . . . . . 18-3

Figure 18-2 Grapher Main Window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-5



Figure 18-5 Grapher Print Window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-12

Figure 18-6 Example of a 3D Display Style Graph . . . . . . . . . . . . . . . . . . . . 18-14

Figure 18-7 Example of a 2D Display Style Graph . . . . . . . . . . . . . . . . . . . . 18-15

Figure 19-1 Object Configuration Tool Window . . . . . . . . . . . . . . . . . . . . . . 19-5

Figure 19-2 Router Configuration Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-9

Figure 19-3 Delete Description Field Window. . . . . . . . . . . . . . . . . . . . . . . . 19-10

Figure 19-4 CMIP Configuration Window . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-12

xxviii Solstice Enterprise Manager Reference Manual

Figure 19-5 MIS Configuration Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-14

Figure 19-6 RPC Configuration Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-16

Figure 19-7 SNMP Configuration Window . . . . . . . . . . . . . . . . . . . . . . . . . . 19-19

Figure 20-1 OBED Main Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-4

Figure 20-2 OBED Properties Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-6

Figure 20-3 Object Configuration Window . . . . . . . . . . . . . . . . . . . . . . . . . . 20-10

Figure 20-4 Action Pull-Right Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-12

Figure 20-5 Action Dialogue Window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-13



Figure D-1 Scoping and Filtering: Hierarchy of Managed Objects . . . . . . D-2

xxix

Tables

Table P-1 Typographic Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxxviii

Table P-2 Shell Prompts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxxix

Table P-3 User Interaction Equivalents . . . . . . . . . . . . . . . . . . . . . . . . . . . . xl

Table 1-1 Solstice EM Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-8

Table 1-2 Solstice EM API Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-10

Table 3-1 Optional Parameters for the GDMO Compiler . . . . . . . . . . . . . 3-9

Table 3-2 cooptoolsschema.asn1 file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-16

Table 5-1 Log Object Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-3

Table 5-2 Default Alarm Types and Log Record Types . . . . . . . . . . . . . . 5-5

Table 5-3 Log Record Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-16

Table 5-4 Database Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-17

Table 5-5 Sample emTable. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-18

Table 5-6 Sample attributeValueChangeRecord Table . . . . . . . . . . . . . . . 5-18

Table 5-7 eventLog Table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-19

Table 5-8 objectCreationRecord Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-20

Table 5-9 objectDeletionRecord Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-20

xxx Solstice Enterprise Manager Reference Manual

Table 5-10 emAlarmRecord Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-21

Table 5-11 attributeValueChangeRecord Table . . . . . . . . . . . . . . . . . . . . . . 5-22

Table 5-12 relationshipChangeRecord Table . . . . . . . . . . . . . . . . . . . . . . . . 5-22

Table 5-13 emInternetAlarmRecord Table . . . . . . . . . . . . . . . . . . . . . . . . . . 5-22

Table 5-14 nerveCenterAlarmRecord Table . . . . . . . . . . . . . . . . . . . . . . . . . 5-23

Table 6-1 Alarm Log Record Processing Options . . . . . . . . . . . . . . . . . . . 6-12

Table 7-1 Optional Parameters for the em_mismgr Command . . . . . . . 7-10

Table 9-1 Access Control Variables in EM-config File . . . . . . . . . . . . . . 9-4

Table 9-2 Super User and Trusted Host Variables in EM-config . . . . . 9-5

Table 10-1 View Properties Default Settings . . . . . . . . . . . . . . . . . . . . . . . . 10-22

Table 10-2 Command Macros . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-43

Table 10-3 Variable Macros . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-44

Table 10-4 Obsolete Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-45

Table 10-5 Viewer Configuration File — View PropertiesParameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-68

Table 12-1 dataCollector GDMO Class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-14

Table 12-2 dataCollectorEntry GDMO Class . . . . . . . . . . . . . . . . . . . . . . . . 12-15

Table 12-3 requestInfo Attribute Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-16

Table 13-1 Log Object Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-2

Table 13-2 Options for the em_logmgr Command. . . . . . . . . . . . . . . . . . . 13-5

Table 13-3 Format Specifier Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-15

Table 13-4 Operator Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-16

Table 13-5 Notification Types and Numbers . . . . . . . . . . . . . . . . . . . . . . . . 13-17

Table 13-6 Sample Log Manager Configuration File. . . . . . . . . . . . . . . . . . 13-24

Table 14-1 Sample Log Viewer Configuration File . . . . . . . . . . . . . . . . . . . 14-21

Table 15-1 Default Alarm Severity Color Mapping. . . . . . . . . . . . . . . . . . . 15-4

Tables xxxi

Table 15-2 Filter Configuration File Statement Types. . . . . . . . . . . . . . . . . 15-35

Table 15-3 Sample View Properties Configuration File . . . . . . . . . . . . . . . 15-36

Table 15-4 Sample Tools Properties Configuration File . . . . . . . . . . . . . . . 15-41

Table 19-1 Object Types and Configurable Data . . . . . . . . . . . . . . . . . . . . . 19-7

Table 23-1 em Command Line Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-2

Table 23-2 em_accesscmd Command Line Options . . . . . . . . . . . . . . . . . 23-3

Table 23-3 em_accessmgr Command Line Options . . . . . . . . . . . . . . . . . 23-6

Table 23-4 em_alarmmgr Command Line Options . . . . . . . . . . . . . . . . . . 23-6

Table 23-5 em_asn1 Command Line Options . . . . . . . . . . . . . . . . . . . . . . . 23-7

Table 23-6 em_autod Command Line Options . . . . . . . . . . . . . . . . . . . . . . 23-8

Table 23-7 em_cmib2gdmo Command Line Options . . . . . . . . . . . . . . . . . 23-8

Table 23-8 em_datacollector Command Line Options . . . . . . . . . . . . 23-11

Table 23-9 em_datad Command Line Options . . . . . . . . . . . . . . . . . . . . . . 23-12

Table 23-10 em_dataviewer Command Line Options . . . . . . . . . . . . . . . . 23-12

Table 23-11 em_debug Command Line Options . . . . . . . . . . . . . . . . . . . . . . 23-14

Table 23-12 em_debug Debug Agents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-14

Table 23-13 em_discover Command LIne Options . . . . . . . . . . . . . . . . . . . . 23-16

Table 23-14 Monitor Command Line Options . . . . . . . . . . . . . . . . . . . . . . . . 23-18

Table 23-15 Discover Debugging Command Line Options . . . . . . . . . . . . . 23-19

Table 23-16 Discover Debugging Command Line Options . . . . . . . . . . . . . 23-19

Table 23-17 em_gdmo Command Line Options . . . . . . . . . . . . . . . . . . . . . . . 23-20

Table 23-18 em_imex Command Line Options . . . . . . . . . . . . . . . . . . . . . . . 23-22

Table 23-19 em_log2rdb.< database> Command Line Options . . . . . . . . . 23-24

Table 23-20 em_logmgr Command Line Options. . . . . . . . . . . . . . . . . . . . . 23-25

Table 23-21 em_logview Command Line Options . . . . . . . . . . . . . . . . . . . 23-26

xxxii Solstice Enterprise Manager Reference Manual

Table 23-22 em_mismgr Command Line Options. . . . . . . . . . . . . . . . . . . . . 23-26

Table 23-23 em_ncexport Command Line Options . . . . . . . . . . . . . . . . . . 23-28

Table 23-24 em_ncimport Command Line Options . . . . . . . . . . . . . . . . . . 23-29

Table 23-25 em_nnadd Command LIne Options . . . . . . . . . . . . . . . . . . . . . . 23-30

Table 23-26 Sample Input File for em_nnconfig . . . . . . . . . . . . . . . . . . . . . 23-31

Table 23-27 em_obcodegen Command Line Options . . . . . . . . . . . . . . . . . 23-32

Table 23-28 em_obed Command Line Options . . . . . . . . . . . . . . . . . . . . . . . 23-33

Table 23-29 em_oct Command Line Options . . . . . . . . . . . . . . . . . . . . . . . . 23-34

Table 23-30 em_reqedit Command Line Options . . . . . . . . . . . . . . . . . . . 23-35

Table 23-31 em_services Command Line Options . . . . . . . . . . . . . . . . . . 23-36

Table 23-32 em_snmdb_import Command Line Options . . . . . . . . . . . . . 23-37

Table 23-33 em_snmfwd Command Line Options. . . . . . . . . . . . . . . . . . . . . 23-38

Table 23-34 em_snmpbrowser Command Line Options. . . . . . . . . . . . . . . 23-39

Table 23-35 em_topoimex Command Line Options . . . . . . . . . . . . . . . . . . 23-40

Table 23-36 em_viewer Command Line Options. . . . . . . . . . . . . . . . . . . . . 23-41

Table A-1 nerveCenterAlarm Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . A-2

Table A-2 internetAlarm Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-3

Table A-3 X.733 OSI Alarms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-5

Table A-4 CMIP Security Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-7

Table A-5 snmAlarmEvents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-9

Table A-6 objectDeletion and objectCreation Event Notifications . . . . . . A-11

Table A-7 attributeValueChange Event Notification . . . . . . . . . . . . . . . . . A-12

Table A-8 relationshipChange Event Notification . . . . . . . . . . . . . . . . . . . A-13

Table A-9 stateChange Event Notifications . . . . . . . . . . . . . . . . . . . . . . . . . A-14

Table A-10 SNMP Trap Notification Attributes . . . . . . . . . . . . . . . . . . . . . . A-15

Tables xxxiii

Table B-1 Environment Variables Used by Solstice EM . . . . . . . . . . . . . . B-1

Table C-1 Summary of Default EM File Locations . . . . . . . . . . . . . . . . . . . C-1

Table D-1 Scoped/Filtered Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-3

Table D-2 ASN.1 Filter Notation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-3

Table D-3 Format Specifier Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-5

Table D-4 Operator Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-5

Table D-5 Scoping Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-8

xxxiv Solstice Enterprise Manager Reference Manual

xxxv

Preface

The Solstice Enterprise Manager Reference Manual provides informationpertaining to Solstice Enterprise Manager™, hereafter referred to asSolstice EM™, Management Information Server (MIS) components, functions,and features, as well as the applications/tools packaged with this product.

Who Should Use This BookThis book is written for system administrators responsible for installing andconfiguring the Solstice EM Management Information Server (MIS) and itsrelated functions as well as for application users of the Solstice EM product.

Before You Read This BookIf you have just acquired Solstice EM, you should read the Solstice EnterpriseManager 2.0 Release Notes for information on installing and starting,compatibility and minimum machine and software requirements, knownproblems, an inventory of the product components, and late breakinginformation about the Solstice EM product.

How This Book Is OrganizedThis document is organized as follows:

Part 1 of this document describes the “Core Functionality” of the Solstice EMproduct.

xxxvi Solstice Enterprise Manager Reference Manual

Chapter 1, “Enterprise Manager Overview,” provides an introduction to thecomponents of Solstice EM and their architectural relationship.

Chapter 2, “Management Information Server (MIS),” provides information onthe Management Information Server (MIS).

Chapter 3, “Compilers,” provides information on the ASN.1, GDMO, ConciseMIB, and Schema compilers.

Chapter 4, “Management Protocol Support,” provides information on theCMIP Management Protocol Adaptor (MPA) and the SNMP and RPC ProtocolDriver Modules (PDMs).

Chapter 5, “Log Management,” provides information on the loggingmechanism.

Chapter 6, “Alarm Service,” describes the MIS Alarm Service, which controlsfault status indication in the EM Viewer.

Chapter 7, “MIS to MIS Communication,” describes the use of the MISManager, which is used to set up and take down connections betweenManagement Information Servers.

Part 2 of this document describes the “Applications” provided with SolsticeEM.

Chapter 8, “Application Launcher,” provides information on the ApplicationLauncher and to how to start applications from its window, as well as how toadd, modify, and delete application icons to/from the Application Launcher.

Chapter 9, “Access Manager,” provides information on using Access Managerto set up groups and user accounts which control user access privileges withinSolstice EM.

Chapter 10, “Viewer,” provides information on the tools used to displaygraphical views of managed resources.

Chapter 11, “Discover,” provides information on using Discover to configurethe Solstice EM database with hosts, routers, networks, and Simple NetworkManagement Protocol (SNMP) devices to be managed.

Chapter 12, “Data Collector,” provides information configuring DataCollection Entry objects.

Preface xxxvii

Chapter 13, “Log Manager,” provides the capability to create and modify logobjects to record event notifications.

Chapter 14, “Log Viewer,” provides the capability to browse through each logrecord within each log object.

Chapter 15, “Alarm Manager,” provides information on monitoring the alarmsreports that have been sent to the MIS.

Chapter 16, “SNMP Browser,” describes the functions of the SNMP MIBBrowser, which allows you to inspect and alter SNMP MIBs.

Chapter 17, “Data Viewer,” provides information on building and making datarequests to a specified object.

Chapter 18, “Grapher,” provides information on the Grapher functions.

Chapter 19, “Object Configuration Tool,” provides information on configuringand browsing the attributes of a Viewer’s object.

Chapter 20, “Object Editor/Browser,” provides information on the OBED toolused for editing and inspecting ASN.1, GDMO, SNMP, and Concise MIBobjects.

Chapter 21, “Topology Import/Export Tool,” describes the TopologyImport/Export Tool, which allows you to save and reload your runtimedatabase when you re-initialize the MIS.

Chapter 22, “Automatic Management,” provides information on configuringand starting/stopping the automatic management function.

Chapter 23, “Command Line Options,” provides a summary of the commandline options for all Solstice EM applications, daemons, and utilities.

Appendix A, “Standard Event Notifications,” describes the structure of thestandard event notification types defined in Solstice EM MIS at installation.

Appendix B, “Environment Variables,” provides a list and description of theenvironment variables used by Solstice EM.

Appendix C, “Enterprise Manager File Structure,” describes the defaultlocations of the files that comprise the Solstice EM product.

Appendix D, “CMIS Scoping and Filtering,”provides information on how touse CMIS scoping and filtering in Solstice EM.

xxxviii Solstice Enterprise Manager Reference Manual

Appendix E, “Additional Sources of Information,” lists standards documentsrelated to network management produced by standards bodies such as ISOand the Network Management Forum.

A Glossary is provided with this document.

Conventions Used in This BookThis section describes the conventions used in this book.

What Typographic Changes and Symbols Mean

The following table describes the type changes and symbols used in this book.

Table P-1 Typographic Conventions

Typeface orSymbol Meaning Example

AaBbCc123 The names of commands, files,and directories; on-screencomputer output

Edit your .login file.Use ls -a to list all files.system% You have mail.

AaBbCc123 What you type, contrasted withon-screen computer output

system% suPassword:

<AaBbCc123> Command-line placeholder:replace with a real name orvalue

To delete a file, type rm<filename>.

AaBbCc123 Book titles, new words or terms,or words to be emphasized

Read Chapter 6 in User’s Guide.These are called class options.You must be root to do this.

Preface xxxix

Shell Prompts in Command Examples

All command line examples in this guide use the C-shell environment. If youuse either the Bourne or Korn shells, refer to sh (1) and ksh (1) man pages forcommand equivalents to the C-shell. The following table shows the defaultsystem prompt and superuser prompt for the C shell, Bourne shell, and Kornshell.

User Interface ConventionsThe following subsections discuss conventions that apply to the descriptions ofthe Solstice EM applications.

Mouse/Menu Interactions

We have pursued a minimalist approach in describing a user’s interactionswith the graphical-based applications in Solstice EM. That is, rather than write:

To exit, press the right mouse button on the File icon. In the pull-downmenu that you receive, move the mouse pointer down to Exit and releasethe right mouse button.

We write:

To exit, select File➤Exit.

The symbol ➤ indicates moving down a level, from a button or icon to a menu,or from one menu to another.

Table P-2 Shell Prompts

Shell Prompt

C shell prompt machine_name%

C shell superuser prompt machine_name#

Bourne shell and Korn shellprompt

$

Bourne shell and Korn shellsuperuser prompt

#

xl Solstice Enterprise Manager Reference Manual

The interface to the Solstice EM applications is, with the except of the ObjectEditor, standard Motif. Selections are made in the identical way they are madefor Motif applications that run on Sun and non-Sun machines.

The following table compares the exhaustive description of a user interactionwith the way we have chosen to describe that interaction in this manual:

Tear-off Menus

The top-level menus in the Solstice EM applications—those applicationsaccessible through the Application Launcher, plus others—have a type of menuknown as a “tear-off” menu. When you select a button, you receive a menuwith a dotted line at the top. If you click left on that dotted line, the menu“tears off”, like a sheet of paper from a tablet, and positions itself in a separatewindow. If you are running the application in a Motif environment, the titledisplays as “<menu title>—Tear-off”. If you are not in a Motif environment, thetitle displays as “No Name”.

To dismiss a tear-off menu, select the menu title bar to obtain a menu ofoptions. In that menu, select Dismiss. Alternatively, you can simply press Escwhile your mouse pointer is in the tear-off menu window.

Table P-3 User Interaction Equivalents

Complete Description As Described in this Document

Select an item by clicking once with the left mouse button. Select an item.

Activate an item by double-clicking with the left mousebutton.

Activate an item.

Press left on the slider in the scrollbar move the slider sothat the item comes into view.

Scroll until the item comes into view.

Press right on the icon to obtain the icon pulldown menu.Move the mouse pointer over the item in the menu andrelease the mouse button.

Select icon➤item.orInvoke icon➤item.

Press and hold middle mouse button on the icon. Move themouse pointer to the target location and release the mousebutton.

Drag and drop.

Preface xli

Connecting to an MIS

All Solstice EM applications rely on a connection with the productkernel—called the Management Information Server or MIS—for their data. Allof the Solstice EM applications can connect to an MIS on a local or remotemachine. When reading the descriptions of the applications in this manual,keep these facts in mind:

• that an application must have a connection to a running MIS;

• that an MIS can be on a local or remote machine.

When connecting to a remote MIS, you can use either of two methods. Thesetwo methods are described below, using the Application Launcher, invokedfrom the em command, as an example.

• Invoke the application with the -host option. For example:

• Set the $EM_SERVER environment variable to the name of the remote MISmachine. For example:

Note that we use C-shell syntax for specifying the environment variable. Usethe syntax appropriate for your shell.

If you invoke an application without the -host option and with theEM_SERVER variable not set, the application attempts to connect to an MIS onthe local machine.

% em -host < remote MIS machine> &

% setenv EM_SERVER < remote MIS machine>% em &

xlii Solstice Enterprise Manager Reference Manual

Part 1 — Core Functionality

1-1

Enterprise Manager Overview 1

Solstice Enterprise Manager (Solstice EM) is a standards-based, object-oriented,distributed network management platform that allows you to monitor,evaluate, and refine your network. It provides tools for performing commonnetwork management tasks, such as fault management, performancemanagement, and configuration management, and includes an applicationprogramming interface that allows developers to integrate Solstice EMcapabilities into their network management environment.

1.1 Solstice EM Features and FunctionsSolstice EM provides the following features and functions:

• Provides support for Common Management Information Protocol (CMIP),Simple Network Management Protocol (SNMP), and SunNet ManagerRemote Procedure Call (RPC) protocol, as well as full conformance withTelecommunications Management Networks (TMN) standards.

Solstice EM Features and Functions page 1-1

Solstice EM High-Level Components page 1-2

Solstice EM Management Information Server (MIS) page 1-3

Solstice EM Applications page 1-7

Solstice EM Application Programming Interface (API) page 1-9

1-2 Solstice Enterprise Manager Reference Manual

1

• Supports multiple concurrent users

• Supports open and proprietary legacy protocols (RPC, SNMP, and CMIP)

• Provides complete compatibility with Solstice Site/Domain Manager andprevious versions of SunNet Manager (2.2 or later).

• Includes a set of GUI (graphical user interface) applications for managingnetworks along with complete, integrated online Help for those applications

• Provides a complete application programming interface (API) fordeveloping user-specific applications that integrate easily with the EMplatform

1.2 Solstice EM High-Level ComponentsThe Solstice EM environment contains the basic elements shown in Figure 1-1.

Figure 1-1 EM High-Level Components

Management Information Server

Network Agents(RPC, SNMP, CMIP)

X-Server

Solstice EM ApplicationsUser-developed Applications

Application ProgrammIng Interface

Other support functions

CMIP over TCP/IP connection

Enterprise Manager Overview 1-3

1

Items shown in the figure with a heavy border are discussed in more detail inthis chapter. Items shown with a light border might be obtained outside ofSolstice EM, but are required for Solstice EM to function appropriately. Itemsshown with a dashed border are optional components that you may choose toadd to your Solstice EM environment.

1.3 Solstice EM Management Information Server (MIS)The basic function of the Solstice EM MIS is to make data about managedobjects available to its clients (applications and services). To do this, theSolstice EM MIS provides the following:

• Maintains the Management Information Tree (MIT), a tree structure ofinformation about managed objects, and supports dynamic creation,maintenance, and deletion of objects in the tree.

• Provides storage for descriptions of managed resources in the MetaDataRepository (MDR). The definition language used to describe networkresources internally is the Guidelines for the Definition of Managed Objects(GDMO), outlined in the ITU X.722 ISO/IEC 10165-4 standard. The MDRcontains a definition for every object element known to the MIS. This dataencompasses everything from the syntax required to refer to an attribute tothe composition of an object package. The MIS allows dynamic updates tothe MDR.

• Provides protocol and location transparency. A client provides an objectname, and the Solstice EM MIS figures out what protocol to use to access theobject, and what address to use within that protocol. This transparencyimplies automatic routing and translation of requests from clients, so theclients themselves have no need to know where an object is physicallylocated or what protocol to use to communicate with it.

• Coordinates requests from multiple clients.

• Provides persistent storage for local data. Data survives shutdown of theMIS. The Solstice EM MIS stores persistent objects in a database.

• Provides distributed multi-user access to data in the MIS and out in thenetwork.

• Provides event handling for SNMP traps and events, and a registrymechanism that allows applications and objects to register interest in anevent.


1

• Provides schema- and MIB-to-GDMO compilers.

• Provides object management services for local objects and representsmanaged objects in a way that takes advantage of object-orientedprogramming techniques.

• Supports both ISO-based naming of managed objects (such as that fromOMNIPoint), and Internet-based naming of the equivalent objects (such asthat provided by MIB-II and its derivatives).

• Provides OSI Log Management Services.

The Solstice EM MIS also provides the resources used by a group of clientapplications for topology discovery (Discover), view management (Viewer),network event correlation (Nerve Center and Request Designer), and loggingservices (Log Manager).

Like a Solaris daemon, the Solstice EM MIS normally runs all of the time. TheSolstice EM MIS runs on one or more of the network’s workstations. The MISdoes not require that this workstation be dedicated to it. However, managing anetwork with Solstice EM requires at least one MIS to be running. It is alsopossible to run more than one Solstice EM MIS within the same network.

1.3.1 Access to Data in the MIS

The central function of the Solstice EM MIS is to make data regarding managedobjects available to its client services. The term managed objects includes boththe physical resources connected to the network (hosts, bridges, routers, and soon), and also conceptual objects (such as links, circuits, and queues). It alsoincludes any objects an application may choose to create: requests, views,counters, lists, collections, and so forth.

All managed objects are accessed through the MIT. There is one global tree,and that tree provides a single naming scheme for all data. The MIT isconstructed according to rules provided by OMNIPoint. The tree has a singleroot (called root). The shape of the tree is arbitrary, and may vary considerablyfrom one Solstice EM MIS to another. The tree’s structure representscontainment relationships. That is, below an object, one finds those objects thatin some sense are related to it.

Data from managed resources (including MIB data) are also a part of the MIT.The Solstice EM MIS makes this data accessible both through the namingconventions that come from the managed resources it describes, and through a


1

resource-independent naming convention, in which identifiers are specifiedusing Fully Distinguished Names (FDNs). It is this mechanism that enables theSolstice EM MIS to achieve transparency of location.

1.3.2 Object Orientation

Object orientation is central to the Solstice EM product, which takes advantageof object-oriented design in two complementary ways:

• It describes managed objects in terms of OMNIPoint and ISO terminology.

• It uses C++ objects for internal storage and manipulation of network data.

The Solstice EM MIS uses one or more C++ classes to correspond directly tothe classes used in the formal descriptions. The following terminology is used:

• Class refers to a C++ class as described in The Annotated C++ ReferenceManual1.

• Instance refers to the memory which is allocated for a C++ class according toits definition. A variable name is usually associated with a particularinstance of a class.

• Managed resource refers to an actual physical device or entity that exists in anetwork or system. This is consistent with the OSI/Network ManagementForum (NMF) definition of this term.

• Managed Object (MO) refers to a set of services and attributes that describesa type of managed resource. Again, this is consistent with the OSI/NMFdefinition for this term.

• Managed Object Class (MOC). This is a term used within the Solstice EMdevelopment environment to refer to the internal representation of amanaged object (as defined by OSI/NM Forum). An MOC is based on theGDMO description. The GDMO definition could be a translate of an SNMPMIB or SunNet Manager schema description. Put another way, the MOCrepresents the attributes and behaviors for particular types of manageableobjects. The MOC defines the type of data stored and the behaviors that canbe taken, but does not represent actual data for any managed object. TheMOC is the internal representation used by the Solstice EM MIS.

1. Annotated C++ Reference Manual, Margaret Ellis and Bjarne Stroustrop. Addison-Wesley Publishing Co.,Reading, MA. Copyright 1990 by AT&T Bell Telephone Laboratories.


1

• Managed Object Instance (MOI) relates to a managed object class in the sameway as an instance relates to a class. The MOC determines the type ofattributes and behaviors available to operate on an object of this type; anMOI refers to actual data which represents an object which is beingmanaged by the MIS. An MOI is also an internal representation used by theSolstice EM MIS.

1.3.3 ASN.1 Definitions

Both in its CMIS-like messages and in data storage for managed objects, theSolstice EM MIS makes extensive use of an ISO standard description of theway data is represented. The description is called ASN.1 (Abstract SyntaxNotation One). A message that uses ASN.1 encoding must include not only theencoded data, but also information about the type of the encoded information.A process that represents a value by an ASN.1 encoding, or that extracts avalue from an ASN.1 encoding, must be able to access the definition of theparticular encoding employed. The GDMO descriptions of new objects alsomake reference to ASN.1 descriptions of their data. t startup, the Solstice EMMIS loads these ASN.1 type files into the MDR. Refer to the “Command LineOptions” chapter in the Solstice Enterprise Manager Reference Manual for detailedinformation about ASN.1 documents and how they are compiled.

1.3.4 Transparent Access to the Distributed Storageof Managed Objects

A managed resource can reside anywhere in the network. The MIS’s MITserves as a map of all the information in the network. It contains an entry forevery managed object known to the Solstice EM MIS. For each managed object,the MIT contains data about the route by which the MIS can get the managedinformation, including objects whose information is stored in the Solstice EMMIS itself, referred to as local objects.

To access objects whose information is stored outside the MIS, the MIT usesremote objects. The MIT’s representation of a remote object containsinformation about the protocol and the address of the remote node wherecurrent information may be found. When getting or setting informationregarding a remote object, the MIS redirects the request to the appropriateagent on the network — an operation that is transparent to the user.


1

Redirection may also require a protocol translation. Where a managed object isreported by an agent that is limited to SNMP, the MIT manager softwarecreates a proxy agent. Although the proxy accepts CMIP-based requests andreturns CMIP-based responses, it uses SNMP to communicate with the remoteagent. The translation between CMIP and SNMP is carried out by the SNMPProtocol Driver Module (PDM) in the MIS. Because CMIP provides facilitiesthat are not directly supported in SNMP, the SNMP PDM is considerably morethan a translator. For example, to support CMIP scoping, the proxy may haveto generate multiple requests and coordinate multiple responses.

In a similar manner, the MIT manager software creates an internal proxy agentto represent the ability of network resources to be managed by SunNetManager Remote Procedure Call (RPC) protocol. An RPC PDM in the MIStranslates internal CMIP-based requests and returns CMIP-based responseswhile using RPC to communicate with the remote agent.

A Solstice EM service can refer to any object that has an entry in the MIT. Theservice does not need to know how the MIS communicates with the managedobject. In particular, it addresses remote objects or proxies in the same way asother managed objects.

1.4 Solstice EM ApplicationsA Solstice EM client is an application or service that is a separate process fromthe Solstice EM MIS. The Solstice EM MIS can accept multiple concurrentclients. A client can reside on the same workstation as the Solstice EM MIS, oron any workstation that communicates with the MIS by way of standardmanagement protocols, including CMIP over the ISO stack, and CMIP overTCP/IP.

An application interacts with standard objects in the Solstice EM MIS, whichcontain information about the network, its topology, and its managed objects.Typically, a client-centered application requests information already in the MISand operates on the responses. It can also subscribe to the MIS’s event-reporting facilities and operate on the event reports it receives.

Solstice EM provides a set of applications that interact with the Solstice EMMIS as client services. These applications are listed in Table 1-1. For eachapplication listed, details on using the application are available in the specific


1

chapter for that application in the Solstice Enterprise Manager Reference Manual.Most of these applications can be started from the main EM GUI, theApplication Launcher, and can also be started directly from the command line.

Table 1-1 Solstice EM Components

Component Name Description

Application Launcher The Application Launcher is the key graphical user interface (GUI) EMprovides for users to manage their networks. The Launcher provides accessto a set of existing EM applications and allows users to add and removeapplications from it.

Access Manager The Access Manager allows users to control access to Solstice EMapplications and their features.

Alarm Manager The Alarm Manager allows the user to examine alarm logs and acknowledgeor clear alarms.

Data Collector Data Collector enables you to create data requests to collect performancedata on selected objects.

Data Viewer The Data Viewer enables you to get, view, modify, and set managementinformation for CMIP and RPC-managed objects.

Discover Discover provides a simple and convenient way to add managed objects tothe MIS database. It uses Internet protocols to find out what devices are on aTCP/IP network and may be used to monitors that configuration.

Grapher The Grapher provides the capability to display data graphically. It isinvoked from the Alarm Manager application.

Log Manager The Log Manager enables you to create, modify, and delete log objects. Youcan define which events are logged to which logs.

Log Viewer The Log Viewer enables you to browse the contents of log records. Logrecords provide detailed information on events that have occurred on yournetwork.

MIS Manager MIS Manager allows you to set up communication between two MISs (ontwo physically separate hosts).

Object ConfigurationTool (OCT)

The OCT allows you to configure and browse the attributes of a managedobject in the Viewer.

Object Editor (OBED) OBED allows you to view, create and delete objects in a Solstice EM MIS’sManagement Information Tree (MIT) and perform gets and sets.


1

1.5 Solstice EM Application Programming Interface (API)In addition to the applications shipped with Solstice EM, users can define theirown applications that interact with the Solstice EM MIS through theApplication Programming Interfaces (APIs) that ship with Solstice EM.

If an application developer also provides access to a managed object type notpreviously known to the MIS, the MIS must be informed of the ManagedObject Class through the use of GDMO and ASN.1 documents.

The Solstice EM APIs provide a rich set of functions for the applicationprogrammer. The libraries, written in C++, contain the objects and methodsnecessary to communicate with the MIS and obtain information about themanaged resources it controls. The APIs provide the following services:

• Initialization, including establishment of a distributed message passinginterface to the MIS

• Event subscription

• Remote caching and cache control

• Local object cache management for applications

• Encoding/decoding of parameters into ASN.1

Request Designer The Request Designer allows you to create request templates. Requesttemplates define the particulars of a request. Request are a series of activitiesthrough which Solstice EM polls for the attributes of managed objectsand/or receives notifications from the agents of managed objects.

SNMP MIB Browser The SNMP Browser enables you to view attributes and view or modifyattribute values for SNMP MIBs managed by Solstice EM.

TopologyImport/Export Tool

The Topology Import/Export Tool allows you to export all or part of thetopology node hierarchy on one or more connected MISs to an ASCII file.This file can then be imported to other MISs in order to recreate the topologynode hierarchy that existed on the original system.

Viewer Viewer provides a visual representation of your network (often referred to asits topology). It enables you to create, inspect, and monitor views.

Table 1-1 Solstice EM Components

Component Name Description


1

• Encoding and encapsulation of data into a format (message class) passed tothe MIS

1.5.1 API Modules

The Solstice EM APIs consist of several different groupings or modules, assummarized in Table 1-2. For details information on developing applicationsthat interact with Solstice EM, see the Solstice Enterprise Manager ApplicationDevelopment Guide. For detailed information about the syntax of specific APIcalls, see the Solstice Enterprise Manager API Syntax Manual.

Table 1-2 Solstice EM API Modules

API Module Description

High-Level PMI(ProgrammingManagement Interface)

For most applications, all interaction with the MIS can be handled throughthe high-level, protocol-independent functions of the PMI. These functionshide the encoding/decoding of ASN.1 values and provide CMIS-likemessages used in communication with the MIS, and (through the MIS) withmanaged objects. It also provides for initialization and for event subscriptionand propagation.

Low-Level PMI The low-level functions are used to exchange messages between the SolsticeEM MIS and client services using CMIS-like messages (M-GET, M-SET, M-CREATE, M-DELETE, M-EVENT-REPORT, M-CANCEL-GET, and M-ACTION).

Application-to-Application API

The Application-to-Application API allows applications to send messages toother EM applications through an emApplicationInstance object.

Grapher API The Grapher API allows developers to create their own graphicalrepresentations of data.

Nerve Center Interface(NCI) Library

NCI is a programmatic interface for controlling Nerve Center operation. TheNCI library enables applications to create, edit, and launch Nerve Centerrequests.

Object Services API The Object Services API allows developers to access services provided bythe EM MIS to implement intra-object behaviors or specialized behaviors.

Topology API The Topology API allows developers to create applications for the EMplatform without learning the details of the MIT topology naming tree.

Viewer API The Viewer API allows applications to communicate with the EM Viewer tocontrol specific Viewer features. This allows developers to leverage Viewerfunctionality and to integrate their applications with the Viewer.


1

1.5.2 Application Development Support Tools

In addition to the API classes and methods, Solstice EM provides the followingprogramming support tools:

• Object Development Tools—Object Development Tools (ODT) provides asimple and automated framework developers can use to add and writebehaviors for managed objects that reside in the MIS. For detailedinformation, see “Developing Object Behaviors” in the Solstice EnterpriseManager Application Development Guide.

• Compilers—Solstice EM includes several compilers that developers or, insome cases, network administrators need to use. These compilers provides ameans for you to add new managed object definitions to the MIS. EMincludes the following compilers:• ASN.1 compiler (em_asn1) which lets you compile descriptions of

managed objects into the MDR. These descriptions are provided in ASN.1documents.

• GDMO compiler (em_gdmo) which you use to compile new GDMOmanaged object description and add them to the MDR.

• Concise MIB compiler (em_cmib2gdmo) which lets you convert an objectdescription written in the Internet Concise MIB format to GDMO for useby EM

• Schema compiler (em_snm2gdmo) which lets you convert an objectdescription written in SunNet Manager schema format to GDMO for useby EM

• em_debug—Solstice EM includes a dynamic debugging function(em_debug). This function helps you track information into and out of theMIS to find out when something is going wrong.


1

2-1

Management Information Server(MIS) 2

2.1 OverviewThe Solstice EM Management Information Server, or MIS, is a single UNIXprocess that runs continuously as a background task on one or moreworkstations attached to a network. It is neither owned nor launched by thevarious applications that use its services, and it communicates with agentslocated in the various devices whose behavior it monitors or manages.

Applications utilize the object services of the MIS by connecting to it over thePortable Management Interface (A C++ application programmer’s interface),or PMI. Once connected, the applications can create, delete, update, initiateaction, register for events, or request data from local or remote objects. Themain function of the MIS is to make data regarding managed objects availableto its clients. In order to do this, the MIS:

Overview page 2-1

MIS Subcomponents page 2-3

Starting the Solstice EM MIS page 2-8

Terminating the Solstice EM MIS page 2-13

Starting the CMIP MPA Daemon page 2-13

Backing Up and Restoring the Runtime Database page 2-14

How to Run the MIS as Non-Root page 2-14


2

• Maintains the Management Information Tree (MIT), which is a treestructure of information about managed objects supporting dynamiccreation, maintenance, and deletion of objects through the PMI (Refer to theSolstice Enterprise Manager Application Development Guide for detailedinformation about the PMI.)

• Provides protocol and location transparency of software models of managedresources, called “managed objects” (An application provides, through thePMI, a managed object name which the MIS uses to determine whatprotocol to use to access the object and the address of the object to usewithin that protocol.)

• Provides persistent storage for local data

• Provides distributed multi-user access to data in the MIS and on thenetwork via the PMI

• Provides event handling and forwarding of traps and events and a registrymechanism (an Event Forwarding Discriminator) that allows applicationsand objects to register for notification of all events and traps

• Provides a repository of management definitions (GDMO and MIBmetadata) that can be used by applications to inquire about the objectsavailable to it (Refer to Chapter 3, “Compilers,” for detailed information.)

• Provides a repository for transfer (ASN.1) syntax for managed objects thatcan be used by applications to encode and decode management information

• Provides object management services for managed objects, and representsmanaged objects in a way that takes advantage of object orientedprogramming techniques

• Supports ISO naming of managed objects

• Provides a proxy mechanism for writing protocol translators for managingobjects not accessible through SNMP or CMIP (Refer to Chapter 4,“Management Protocol Support,” for detailed information.)

• Provides the Nerve Center Interface (NCI) library that supports user-defined intructions for detecting conditions and events in the network andtaking actions in response to those conditions and events (Refer to theSolstice Enterprise Manager API Syntax Manual for detailed information.)

The Solstice EM MIS provides a set of management functions and anenvironment for implementing and manipulating managed objects.

Management Information Server (MIS) 2-3

2

Management applications direct managed resources through requeststransmitted to the MIS via the PMI. Subsequently, the MIS returns the results ofthe commands to the application via the PMI.

The information associated with a management request consists of:

• An operation

• A target object

• Zero or more parameters

These management requests permit:

• Creation and deletion of managed objects

• Searching the Management Information Tree (MIT) for a managed objectthat meets certain filtering criteria

• Fetching the value of a managed object’s attribute

• Changing a value of an attribute

• Invoking a special function implemented by a managed object

• Sending or receiving notifications of asynchronous events

2.2 MIS SubcomponentsThe MIS components are described in the following subsections.

2.2.1 Portable Management Interface (PMI)

The MIS uses the PMI to communicate with applications and agents. The PMIcan be broken down into the following areas:

• The user level of the PMI supports the access and maintenance of objectsand object definitions in the MIS.

• The Management Protocol Adapter Library subset of the PMI is used byproxy agent writers needing to access managed objects over protocols otherthan CMIP/OSI or SNMP/IP.

Refer to the Solstice Enterprise Manager API Syntax Manual for more detailedinformation.


2

2.2.2 Management Information Tree (MIT)

Every managed object known to the MIS is represented in the ManagementInformation Tree. The objects in the MIT include network devices such asrouters and hosts, virtual objects such as queues, filters, and events, and objectsthat the MIS itself or applications create. A single global MIT provides a singlenaming scheme for all objects. The MIT is constructed according to standardsspecified by OMNIPoint I (A set of standards, implementation specifications,and tools developed by the Network Management Forum).

2.2.3 MetaData Repository (MDR)

The MetaData Repository (MDR) is a storage area within the MIS holding thedescriptions of managed objects. A description for every object known to theMIS is stored in the MDR. This data encompasses everything from the syntaxreferring to an attribute to the composition of an object package. The MDR isinitialized and updated by using the GDMO and ASN.1 compilers. The MISallows dynamic updates to the MDR. Refer to Chapter 3, “Compilers,” formore detailed information.

2.2.4 Nerve Center

The Nerve Center is the portion of the MIS that detects conditions in a networkand takes actions based on those conditions. The MIS creates manager objectsthat poll managed objects in the network, or listen for event notifications,based on request templates created by applications using the Nerve CenterInterface Library. Applications and users can create request templates, thenhave the MIS apply the templates to a set of managed objects. Refer to theSolstice Enterprise Manager API Syntax Manual for information on the NerveCenter Interface (NCI) Library. The “Nerve Center Overview” chapter of theSolstice Enterprise Manager Administration Guide contains a guide to the SolsticeEM documentation on Nerve Center as well as an overview of Nerve Centercomponents.

2.2.5 CMIP Management Protocol Adaptor

The CMIP Management Protocol Adaptor (MPA) is a separate UNIX processwhich utilizes the PMI to fulfill CMIP requests sent by the MIS. Refer toChapter 4, “Management Protocol Support,” for more detailed information.


2

2.2.6 SNMP Protocol Driver Module

The SNMP Protocol Driver Module (PDM) is the part of the MIS process thatfulfills SNMP requests sent by the MIS. Refer to Chapter 4, “ManagementProtocol Support,” for more detailed information.

2.2.7 RPC Protocol Driver Module

The RPC Protocol Driver Module (PDM) is the part of the MIS process that fillsRPC requests sent by the MIS. This PDM maintains compatibility with SunNetManager (SNM) Agents. Refer to Chapter 4, “Management Protocol Support,”for more detailed information.

2.2.8 Alarm Service Module

The Alarm Service is the central module in the MIS that stores the state ofmanaged objects, and maps the topology nodes which represent them. Refer tothe “Alarm Service” chapter in the Solstice Enterprise Manager Reference Manualfor detailed information.

2.2.9 Persistent Storage

Data local to the MIS is stored in a Unix DBM database. This local data consistsof all objects that are configured to be persistent and are created in the MIS bythe PMI. The persistent storage of MIS objects allows for restarting an MISwithout data or configuration loss, and is transparent to the user.

2.2.10 em_login Daemon

The em_login daemon is a UNIX process that listens to all connectionrequests for password authentication, and is part of the securityimplementation of Solstice EM which allows you to control access to certainapplications. For more information about granting access and setting up userpermissions, see Chapter 9, “Access Manager.”


2

2.2.11 em_mis Daemon

The em_mis daemon implements the majority of the MIS functions. Thisdaemon is started when the em_services command is invoked. Refer toSection 2.3, “Starting the Solstice EM MIS,” for more details.

2.2.12 em_snmp-trap Daemon

The em_snmp-trap daemon is a UNIX process separate from the MIS whichlistens on port 162 for SNMP traps. The traps are converted based on a user-defined mapping to CMIP notifications and forwarded to the MIS. Theem_snmp-trap daemon may be distributed to other hosts on the network. Referto the “Configuring SNMP Trap Processing” chapter in the Solstice EnterpriseManager Administration Guide for detailed information.

2.2.13 em_ncam Daemon

The em_ncam daemon is a UNIX process that handles Nerve Center actionssuch as sending e-mail or executing a UNIX command. This daemon is startedwhen the em_services command is invoked. Refer to Section 2.3, “Startingthe Solstice EM MIS,” for detailed information, or refer to the “Nerve CenterOverview” chapter in the Solstice Enterprise Manager Administration Guide forinformation about the Nerve Center.

2.2.14 em_snmfwd Daemon

The em_snmfwd daemon is a UNIX process that is used to forward SunNetManager (SNM) events to the MIS for processing. The em_snmfwd daemonregisters with the SNM 2.x na.event daemon, receives all events that a SNMconsole would receive, and forwards SNM events as snmAlarmEvents andSNM traps as snmAlarmTraps. No data reports, however, are forwarded. Theem_snmfwd daemon only has an effect if the na.event daemon is running aswell. This daemon is started when the em_services command is invoked aslong as the SUNWembc package has been installed. Refer to Section 2.3,“Starting the Solstice EM MIS,” or to the “Device Management Using SunNetManager Agents” chapter in the Solstice Enterprise Manager AdministrationGuide for detailed information.


2

2.2.15 em_nnmpa Daemon

The em_nnmpa daemon is a UNIX process that starts the gobal nickname (FDNtranslation) server, which is a mapping engine that maps object names (FDNs)into user-defined text. Currently, the Alarm Manager and Log Manager utilizethe global nickname server.

2.2.16 em_cmip Daemon

The em_cmip daemon is a UNIX process that implements CMIP MPAfunctions. It talks to the SunLink CMIP/OSI stack. If OSI has not beeninstalled when the em_cmip daemon is started, an error message to that effectwill be displayed and the em_cmip daemon is not started. This daemon isstarted during product installation when the SUNWemcpa package is installedand CMIP is up and running, as well as whenever the machine theSUNWemcpa package was installed on is rebooted.

2.2.17 em_autod Daemon

The em_autod daemon is a UNIX process responsible for monitoring thecreation and deletion of objects in the MIS, starting requests for newly createdobjects, and stopping requests when objects are deleted. Refer to Chapter 22,“Automatic Management,” for more information about AutomaticManagement and the em_autod daemon.

2.2.18 em_datad Daemon

The em_datad daemon is a UNIX process that can be configured by the DataCollector application to collect performance and accounting data. For moreinformation, see Chapter 12, “Data Collector.”

2.2.19 em_log2rdb. <database_name> Daemon

em_log2rdb. <database_name> is a set of Unix processes that convert theSolstice EM historical log files to relational database tables. In Solstice EM,three em_log2rdb. <database_name> processes are implemented for Sybase,Oracle, and Informix. These processes are em_log2rdb.sybs ,em_log2rdb.orcl , and em_log2rdb.ifmx , respectively.


2

2.3 Starting the Solstice EM MISThe Solstice EM MIS and its associated daemons are started as root byinvoking the em_services command. To see a listing of the optionalcommand line parameters that can be used with this command, use the -helpoption, as shown below.

All invocations of the em_services command start the following Solstice EMdaemons: em_login , em_mis , em_snmp-trap , em_ncam, em_snmfwd ,em_nnmpa, em_autod , and em_datad . However, no invocations of theem_services command start any of the Solstice EM applications. Refer toSection 2.2, “MIS Subcomponents,” for a description of the Solstice EMdaemons.

Note – If you are starting the MIS immediately following a new installation,and you did not have the em_install program automatically start the MIS,you must use the em_serivces -r command. For more information, see theSolstice Enterprise Manager Installation Guide.

# $EM_HOME/bin/em_services -help

em_services starts or stops all the necessary processesto run the Solstice Emterprise Manager MIS.

em_services to restart the platform in the state in which it was last shutdown.em_services -i to start with a new databaseem_services -r to reinitialize the platformem_services -s to kill all daemonsem_services -h print this message#


2

2.3.1 Starting the Solstice EM MIS and Preservingthe Data

To start and/or restart the MIS and preserve the configuration data, invoke theem_services command without any options, as shown below:

Shown below is the output resulting from issuing this command.

2.3.2 Starting the Solstice EM MIS withoutPreserving the Data

To start and/or restart the MIS without saving any of the data in the MIS,invoke the em_services -i command as shown below:

# $EM_HOME/bin/em_services

# ./em_servicesRemoving na.snmp-trap from /etc/inetd.conf for SNM compatibilityInstructing inetd to re-read config file

Terminating all Solstice EM daemonsStarting em_login em_mis em_snmp-trap em_ncam em_snmfwd em_nnmpa em_autodem_datad

Solstice EM (TM) 2.0 Beta (Jun 10 1996) Management Information Server (MIS)

Copyright 1994 - 1996 Sun Microsystems, Inc. All Rights Reserved.Portions of this product are derived from the DiMONS 3G software licensedfrom NetLabs, Inc. Mapping technology and data originate with StrategicMapping, Inc., 3135 Kifer Road, Santa Clara, Ca., 95051, USA(Obtain additional map data from Strategic Mapping Inc., 800-764-3228 in USA).

em_services Start-up Complete.#

# $EM_HOME/bin/em_services -i


2

If you have an existing MIS database, you will see the following question:

Enter y to continue, or n to return to the shell prompt. If you chose to continue,you will receive the output shown below.

The em_services -i command removes all of the data in the MIS. However,you can use the Topology Import/Export Tool to export the topologyinformation to a file. (For more information, see Chapter 21, “TopologyImport/Export Tool.”) Additionally, you can use the em_ncexport utility toexport request templates, conditions, poll rates, and severities. (For moreinformation, see the “Request Designer” chapter in the Solstice EnterpriseManager Administration Guide.

Note – Using the Topology Import/Export Tool backs up topology-relatedinformation only. This tool does not back up your entire MIS database.

When the em_services -i command starts all MIS processes, any previouslycreated data in the MIS is lost.

# ./em_services -iWarning: all current database information will be lost.

Do you want to continue (y/n)?

Terminating all Solstice EM daemonsStarting em_login em_mis em_snmp-trap em_ncam em_snmfwd em_nnmpa em_autodem_datad

Solstice EM (TM) 2.0 Beta (Jun 10 1996) Management Information Server (MIS)




2

2.3.3 Starting the Solstice EM MIS and Reinitializingthe Configuration Data

To start and/or restart the MIS and reinitialize the configuration data, invokethe em_services -r command as shown below:

If a previous version of Solstice EM exists on your machine, you will see thefollowing question:

# $EM_HOME/bin/em_services -r

# ./em_services -rWarning: the platform will be reinitialized.

Do you want to continue (y/n)?


2

Enter y to continue, or n to return to the shell prompt. If you chose to continue,you will receive the output shown below.

2.3.4 Starting the Solstice EM Applications

After you have successfully started the MIS, you are ready to invoke variousSolstice EM applications. Refer to the following documents for moreinformation:

• Solstice Enterprise Manager Reference Manual for information about theSolstice EM functions, core applications, and tools.

• Solstice Enterprise Manager API Syntax Manual for information about theclasses and functions provided by the MIS PMI.

Terminating all Solstice EM daemons<List of Terminated Daemons>Running reinitialization of platformCompiling ASN.1 files..........................................................................Compiling gdmo files ...<List of GDMO Files>reinitialization completeStarting em_login em_mis em_snmp-trap em_ncam em_snmfwd em_nnmpa em_autodem_datad

Solstice EM (TM) 2.0 (Jun 14 1996) Management Information Server (MIS)


Initializing...................................................................................................



2

• Solstice Enterprise Manager Application Development Guide for generalinformation and samples showing how to use the Portable ManagementInterface (PMI) and Nerve Center Interface (NCI) library.

2.4 Terminating the Solstice EM MISTo terminate the Solstice EM daemons (em_login , em_mis , em_snmp-trap ,em_ncam, em_snmfwd, em_nnmpa, em_autod , and em_datad ), invoke theem_services -s command as shown below.

The em_cmip and em_log2rdb. <database_name> daemons will not beterminated. Solstice EM applications that are connected to this MIS will receivea disconnect signal if this command is invoked. Depending upon the particularapplication, some Solstice EM applications may terminate when disconnected.

2.5 Starting the CMIP MPA DaemonTo use the CMIP management protocol, install the CMIP MPA package(SUNWemcpa) and start the CMIP MPA daemon (em_cmip ) as root byinvoking the following command:

Note – The CMIP MPA (em_cmip ) is started automatically during packageinstallation whenever the machine it is installed on is re-booted.

# $M_HOME/bin/em_services -s

# /etc/rc2.d/S98cmipmpa start


2

2.6 Backing Up and Restoring the Runtime DatabaseThe following methods can be used to backup and restore the runtimedatabase environment. First, it is recommended that you stop all Solstice EMdaemons before executing a backup or restore operation. You can do this byinvoking the following command:

To create a backup of the runtime environment, invoke the following commandas root :

To restore a previously backed up runtime environment, invoke the followingcommands as root :

The above dump and restore utilities are used instead of the more commonlyused utilities such as tar or cpio to ensure that the dbm files are copiedcorrectly.

2.7 How to Run the MIS as Non-RootBy default, the MIS is run as root . To configure the MIS so that it is not run asroot , you must perform the following steps:

Note – It is advised that you make backup copies of all relevant files in theevent that you decide not to implement your changes.

1. Add a non-root super-user to be recognized by Access Control as follows:

a. Log in as root .

b. cd to $EM_HOME/build/acct .

# $EM_HOME/bin/em_services -s

# ufsdump 0f < dump_file_or_devices> /var/opt/SUNWconn/em

# cd/# ufsrestore xf < dump_file_or_devices> /var/opt/SUNWconn/em


2

c. Edit the EM-config file, find the following line:

and change it to:

where <username> is the new user login ID.

2. cd to $EM_HOME/bin and modify the file permissions on em_snmp-trap ,em_trapd , and em_mis , as follows:

a. Enter the following command::

b. Enter the following command:

c. Enter the following command:

3. Edit the em_services script to comment out the following lines (byinserting # in the column at the left edge of each line):

4. For a user other than root to run the MIS, the var-install script mustbe modified to enter the <username> of the selected user in certain lines.

EM_ACCESS_SUPER_USERS:

EM_ACCESS_SUPER_USERS: < username>

# chmod 4555 em_snmp-trap

# chmod 4555 em_mis

# chmod 4555 em_trapd

# if test ̀ /usr/bin/id | /usr/bin/awk '{print $1}'` != "uid=0(root)"# then# $ECHO "You must be root user to run em_services."# exit 1# fi


2

a. Edit line 61 as follows:

Replace <username> and <groupname> with the login ID and the groupname of the user, respectively.

b. Edit line 64 as follows:

As before, replace <username> and <groupname> with the login ID andthe group name of the user, respectively.

c. Several of the lines from line 75 through line 85 begin with “copyfile644 bin other ”. In all of these lines, replace “bin ” with the login IDof the user, and “other ” with the user’s group name.

5. If any EM MIS daemons are currently running, invoke em_services -sto stop them. The non-root user can then restart them.

6. If the MIS has previously been run as root , remove the original databasefiles.

When the MIS is restarted via em_services -r , the database files will take onthe file permissions of the user specified by <username> when this user startsthe MIS. To make this change in the database files:

a. Log in as root .

b. Enter the following commands:

c. Log in as normal user under the specified <username>.

makedir 755 < username> < groupname> ${ runtime}

makedir 777 < username> < groupname> \

# rm -rf /var/opt/SUNWconn/em/*# chmod 777 /var/opt/SUNWconn/em# chown < username> /var/opt/SUNWconn/em# chgrp < groupname> /var/opt/SUNWconn/em


2

d. Enter the following command:

Once these steps are completed, only the user specified as <username> shouldrun the MIS to avoid problems related to file permissions.

hostname% em_services -r


2

3-1

Compilers 3

3.1 OverviewThis chapter describes the compilers provided with Solstice Enterprise Manager2.0. These are:

• em_asn1 — ASN.1 compiler

• em_gdmo — GDMO compiler

• em_cmib2gdmo — Concise MIB compiler

• em_snm2gdmo — SunNet Manager 2.2 or later Schema compiler

Note – It is assumed that you installed the Solstice Enterprise Manager in thedefault directory /opt/SUNWconn/em . If you installed the product in adifferent directory, replace all /opt/SUNWconn/em instances in this chapterwith the appropriate directory path.

Overview page 3-1

The ASN.1 Compiler page 3-4

The GDMO Compiler page 3-6

The Concise MIB Compiler page 3-10

The Schema Compiler page 3-15


3

The compilers provide a means for you to add new managed object definitionsto the Management Information Server (MIS). If your application refers only toobject classes already known to the Solstice EM MIS, you will not need to usethese compilers. However, if you plan to add new managed objects to the MIS,you should read this chapter for instructions. Refer also to the chapter entitled“Adding a Managed Object to the MIS” in the Solstice Enterprise ManagerAdministration Guide for additional information.

3.1.1 Management Information Tree (MIT)

Every object known to the MIS is represented in the Management InformationTree (MIT). The objects in the MIT include network devices such as routers andhosts, virtual objects such as queues, filters, and events, and objects that theMIS itself or applications create. A single global MIT provides a single namingscheme for all data. The MIT is constructed according to a standard providedby OMNIPoint 1.

3.1.2 Object Descriptions

A description of every object known to the MIS is stored in the MetaDataRepository (MDR). The data in the descriptions encompasses everything fromthe syntax required to refer to an attribute, to the composition of an objectpackage. The MIS then makes this data available to its clients.

For every managed object known to the MIS, the MIS must have the followinginformation:

• The class to which the object belongs

• The specifics of the instance of that class, such as a list of attributes, thesyntax of each attribute, and the name bindings, which give the object’sposition within the MIT.

The definitions for managed objects are contained in ASN.1 and GDMOdocuments. These are found in the following directories, respectively:

• $EM_HOME/etc/asn1

• $EM_HOME/etc/gdmo

Compilers 3-3

3

These documents are normally compiled and installed into the MDR when youinstall Solstice EM, or when you run the following command:

For more information about the em_services command, see Chapter 2,“Management Information Server (MIS).”

Note – There is one GDMO document associated with a particular managedobject. The document names are usually composed of the name of the managedobject class followed by the suffix .asn1 or .gdmo .

3.1.3 Adding a New Managed Object to the MDR

If you want to add a new definition to the MDR, you must create theappropriate ASN.1 and GDMO documents. You can use existing ASN.1 andGDMO documents as templates for your new documents, or you can writeyour own from scratch. Once you have created these documents, you mustcompile the definitions and add them to the MDR.

The following summarizes the processes handled by each compiler:

• The Abstract Syntax Notation One (ASN.1) Compiler (em_asn1)

This compiler processes a description of a managed object transfer syntaxwritten in ASN.1 type format. Such a description may be produced asoutput from the Concise MIB compiler, from the Schema compiler (seebelow), or can be supplied directly from an ASN.1 document. Refer toSection 3.2, “The ASN.1 Compiler,” for details on using this compiler.

• The Guidelines for the Definition of Managed Objects (GDMO) Compiler(em_gdmo)

This compiler processes a managed object description written in GDMOformat. Such a description may be produced as output from the ConciseMIB compiler, from the Schema compiler (see below), or can be supplieddirectly from a GDMO document. Refer to Section 3.3, “The GDMOCompiler,” on page 3-6,” for details on using this compiler.

• The Concise MIB Compiler (em_cmib2gdmo)

# em_services -r


3

This compiler translates an SNMP MIB into both GDMO and ASN.1formats, thus serving as a preprocessor for both the GDMO and ASN.1compilers. Refer to Section 3.4, “The Concise MIB Compiler,” on page 3-10,for details.

• The Schema Compiler (em_snm2gdmo)

You can use this compiler to translate SunNet Manager 2.2 or later schemafiles to GDMO and ASN.1 format. This compiler serves as a preprocessor tothe GDMO compiler. Refer to Section 3.5, “The Schema Compiler,” onpage 3-15, for detailed information on the Schema compiler.

These compilers are described in more detail in the sections that follow.

3.2 The ASN.1 CompilerYou must use the ASN.1 compiler to compile ASN.1 descriptions of managedobjects (contained in ASN.1 documents), into the MDR. The chapter entitled“Adding a Managed Object to the MIS” in the Solstice Enterprise ManagerAdministration Guide provides examples of this procedure.

3.2.1 ASN.1 Documents

ASN.1 documents contain ASN.1 definitions written in ASN.1 format. Amessage that uses ASN.1 encoding must include not only the encoded data,but also information about the type of encoded information. A process thatrepresents a value with an ASN.1 encoding, or that extracts a value from anASN.1 encoding, must be able to access the definition of the particularencoding employed. The GDMO descriptions of new objects also makereference to ASN.1 descriptions for the syntax of attributes defined within.

To provide effective access to the needed ASN.1 definitions, the Solstice EMMDR keeps a set of files containing type definitions and encoding rules. Whenthe definitions of new objects make reference to new ASN.1 types, filescontaining the new ASN.1 definitions must be included in the MIS ASN1directory. At start-up and periodically thereafter, the Solstice EM MIS loadsthese ASN.1 type files into the MDR.

Solstice EM provides ASN.1 documents for a variety of managed objects. Thesedocuments are located in the directory $EM_HOME/etc/asn1 .

Compilers 3-5

3

3.2.2 Compiling ASN.1 Documents

The ASN.1 compiler compiles the contents of ASN.1 documents into a formatused internally by the MIS. Upon successful compilation, it places the outputfiles into the directory in which the compiler was invoked. You must thenmove or copy the output file into the/var/opt/SUNWconn/em/usr/data/ASN1 MDR user directory.Alternatively, you can use the -o parameter and specify this directory wheninvoking the ASN.1 compiler from the command line.

Invoke the ANS.1 compiler from the command line as follows:

The optional parameters for the em_asn1 command are described below:

3.2.3 See Also

For detailed information on using ASN.1 and the format of ASN.1 definitions,refer to the following reference materials:

• ISO 8824 Specification of Abstract Syntax Notation One (ASN.1)

• ISO 8825 Specification of Basic Encoding Rules for Abstract Syntax NotationOne (ASN.1)

hostname% em_asn1 [-v] [-o < output_dir>] < file> ...

Option Description

-help Print list of options (with descriptions) for the em_asn1command.

-v Specify verbose mode.

-o < output_dir> Specify the directory into which the compiled files are to bewritten. The directory will be created if it does not alreadyexist.

<file> Specify the name of the ASN.1 document to be compiled.Multiple file names may be specified, delimited by a space.


3

3.3 The GDMO CompilerYou can use the GDMO compiler (em_gdmo) to compile new GDMO managedobject descriptions. To add them to the MDR, you must either restart the MIS,or use the -host < hostname> parameter. This then enables the MIS to recognizenew classes of GDMO-defined objects not previously known to it. Forexamples of this procedure, see the chapter entitled “Adding a ManagedObject to the MIS” in the Solstice Enterprise Manager Administration Guide.

3.3.1 GDMO Compiler Input

The GDMO compiler takes as its input one or more object class descriptionswritten in the standard GDMO format. The input must be provided in ASCIItext files. A single file may contain several descriptions; the required format fora description clearly delimits the beginning and end of each. It is permissiblefor a single description to span several files, but this is not recommended.

The format of a GDMO description is described in the ISO/IEC 10165-4specification Information Technology - Structure of Management Information -Part 4: Guidelines for the Definition of Managed Objects. This document includestemplates; that is, sample descriptions of various types of managed objects.These templates may serve as models for the description of specific objects ofthe same general type but with differing particulars.

The GDMO compiler follows the required format very closely and isunforgiving of deviations.

The Solstice EM product provides GDMO documents in the$EM_HOME/etc/gdmo directory. You can use these managed objectdescriptions as is, or you can create your own. If you are creating newmanaged object definitions, note that GDMO documents are generally givenmnemonic names followed by a .gdmo extension. When the GDMO compileris used on these files, it produces one or more output files depending on thecontent of the documents.

Solstice EM provides the user MDR directory/var/opt/SUNWconn/em/usr/data/MDR in which you can store yourprivate compiled GDMO documents. When the MIS is started, it looks forcompiled documents in both this directory and the directory/var/opt/SUNWconn/em /data/MDR , and loads any appropriatedocuments that it finds. For the documents to be loaded into the MDR, they

Compilers 3-7

3

must be in either of these two directories. You can compile the documents inany directory and then manually copy or move then over, or you can specify adirectory using the -output < output_dir> parameter (see Section 3.3.4,“em_gdmo Command Line Syntax”).

3.3.2 Managing Related GDMO Documents

For parsing purposes, all GDMO definitions and documents used by a GDMOdocument should be in the same file. This ensures proper validation acrossdocument boundaries. Parsing GDMO documents as separate files ispermissible, but does not provide cross-validation between files.

Consider an example wherein Document A calls out an attributeoperationalState and states it is defined in Document B. The actualsyntax of operationalState cannot be validated unless Document B is inthe same file. If Document B is a different file, during parsing of Document A,the parser assumes that Document B will be found and will contain what isneeded. If in Document B the attribute name is misspelled (for example,OperationalState rather than operationalState ), the parser cannotvalidate Document B and therefore notes a warning. A warning is not fatal; itwould be reported even if Document B were perfect. Parsing then continues.You may still receive a “parsing complete” message when the information isloaded into the MDR. You would see no errors for Document B. Later, the faultwill manifest as a “no-such-attribute” error when an attempt is made toinstantiate an object whose definition contains the incorrect syntax. This mayalso occur when an attempt is made to display information retrieved from aremote object that uses the invalidated syntax.

3.3.3 GDMO Compiler Output

When the GDMO compiler runs in compile (non-parsing) mode, it reads thesource files, compiles them, and passes the compiled description — via thePMI — to a running Solstice EM MIS. The portions of the description dealingwith object classes, packages, attributes, and name bindings are compiled andstored in the MDR.


3

3.3.3.1 Output Files

The output files are written to the directory in which the compiler wasinvoked. You must then copy or move the output files to the directory/var/opt/SUNWconn/em/usr/data/MDR . Alternatively, you can specifythis directory in conjunction with the -output < output_dir> parameter whenyou invoke the GDMO compiler.

Note – If you invoke the GDMO compiler without the -host < hostname>parameter, the MIS must be restarted in order for the GDMO data to be loadedinto the MDR.

Each output file is assigned a name derived from the source document, excepta space character is mapped to an underscore character, and a slash character ismapped to a percent character.

3.3.3.2 Header Line in the Parsed Document

Each output file must start with a header line. If you invoke the GDMOcompiler with the -header <header_string> parameter, the specified string isused as the first line of the output file. If you omit this parameter, the followingdefault header is used:

3.3.4 em_gdmo Command Line Syntax

Invoke the GDMO compiler from the command line as follows:

The -file < file> parameter is used to specify the input file(s). The optionalparameters for the em_gdmo command are described in Table 3-1.

@(#) Created by <user> at <date>

hostname% em_gdmo [options] -file < file>...

Compilers 3-9

3

Table 3-1 Optional Parameters for the GDMO Compiler

The GDMO compiler functions in two modes of operation:

• Parse-only

• Parse-and-compile

3.3.4.1 Parse-only Operation

Invoke the GDMO compiler as follows so that it uses a grammar parser toverify conformance to syntactic rules:

An error detected by the GDMO compiler during parsing generates a messagestating the name of the file being parsed, and the line number where the errorwas encountered.

3.3.4.2 Parse-and-Compile Operation

Once the input files can be parsed without error, you can run the compiler inthe parse-and-compile mode to store the parsed and compiled definitions inthe MDR directory, then restart the MIS to load the definitions.

Option Description

-help Print list of options (with descriptions) for theem_gdmo command.

-host <server> Specify the name of an MIS server. The compileddefinitions are loaded into the MDR.

-header <string> Specify the header string.

-verbose Specify verbose mode.

-debug Display MIS debugging information.

-parse Specify parse-only operation.

-output < output_dir> Specify the directory into which the compiled files areto be written.

hostname% em_gdmo -parse -file < file>


3

To run the compiler in parse-and-compile mode, invoke em_gdmo as follows:

You then must run em_services to load the definitions into the MDR.Alternatively, you can load the definitions into the MDR directly:

To process the parsed and compiled input, the MIS must refer to ASN.1documents located in the $EM_HOME/etc/asn1 directory. You must be rootto write to this directory. The GDMO descriptions assume that these definitionsare present. Refer to Section 3.2.1, “ASN.1 Documents,” for more informationabout the preparation, storage, and availability of ASN.1 files.

Warning – If the MIS does not have access to the required ASN.1 definitions,the GDMO compiler will not receive an error. Consequently, the problem willnot become evident until later. When a process attempts to instantiate an objectbased on the class description you supplied, or to display informationretrieved from a remote object that used your syntax, it is likely to receive a“no-such-attribute” error, or some other related error.

3.4 The Concise MIB CompilerYou can extend the Solstice EM MIS Management Information Tree (MIT) torecognize new types of managed objects. When a new object description isspecified in a GDMO document, the description can be processed directly bythe GDMO compiler (described in Section 3.3, “The GDMO Compiler,” onpage 3-6). However, when the object description is written in the InternetConcise MIB format, the description must first be processed by the ConciseMIB compiler.

The Concise MIB compiler (em_cmib2gdmo) takes MIBs and generates twofiles in the appropriate formats for the GDMO and ASN.1 compilers. When theresulting GDMO descriptions are parsed and compiled, they make use ofASN.1 descriptions of their data types. The Concise MIB compiler generates a<type>.asn1 file as well as a <type>.gdmo file (refer to Figure 3-1).

hostname% em_gdmo -output /var/opt/SUNWconn/em/usr/data/MDR -file < file>

hostname% em_gdmo -host < hostname> -file < file>...

Compilers 3-11

3

If the target files exist, they are overwritten. You would normally use theConcise MIB compiler (em_cmib2gdmo) in conjunction with the GDMOcompiler (em_gdmo) and the ASN.1 compiler (em_asn1) to take a vendor-specific Concise MIB, convert it to GDMO and ASN.1 components, andincorporate further compiled versions of these into the Solstice EM MIS. TheConcise MIB compiler checks the source files to ensure they conform to RFC1212, and reports any errors that are discovered. The GDMO and ASN.1 outputfiles are produced even if incorrect or incomplete.

By default, em_cmib2gdmo imports the following OIDs from RFC 1155:

• ISO

• ORG

• DOD

• Internet

• directory

• MGMT

• experimental

• private

• enterprises

This importation can be suppressed by using the -1155 option (see“Options,” below). Also, by default, the following types are built in (normallydefined in RFC 1155):

• NetworkAddress

• IpAddress

• Counter

• Gauge

• TimeTicks

• Opaque

The following are also built in (normally defined in RFC 1213):

• OBJECT-TYPE macro

• DisplayString


3

• PhysAddress

Figure 3-1 The Concise MIB Compiler in Context

3.4.1 Names of Input and Output Files

An input file for the GDMO compiler can have any name, but by convention,the name should end with the extension .mib . The Concise MIB compilergenerates two output files for each input file. The output files have the samenames as the input file with the extension (if any) replaced by .gdmo and.asn1 , respectively.

To process the files produced by the Concise MIB compiler:

1. Use the ASN.1 compiler to process the <type>.asn1 file.Refer to Section 3.2, “The ASN.1 Compiler,” on page 3-4 for moreinformation about the ASN.1 compiler.

<type>. asn1file

<type>.gdmofile em_gdmo

EM MIS

etc/MDR

etc/ASN1

em_asn1compiler

em_cmib2gdmocompiler

compiler

InternetSNMPMIB file

Compilers 3-13

3

2. Use the GDMO compiler to process the <filename>.gdmo file.Refer to Section 3.3, “The GDMO Compiler,” on page 3-6 for moreinformation about the GDMO compiler and how to further process the<filename>.gdmo file for inclusion in the MIS.

3.4.2 em_cmib2gdmo Command Line Syntax

Following is the format of the Concise MIB compiler’s command line syntaxand a description of the available options:

The optional parameters for the em_cmib2gdmo command are describedbelow:

-1155Instructs the compiler not to automatically include OIDs from RFC 1155.Normally, the following types from RFC 1155 are automatically defined:ISO , ORG, DOD, Internet , Directory , MGMT, experimental , private ,and enterprise . This is necessary because the translator must resolveOIDs to full numerical paths. Since almost all MIBs use one or more of theseOIDs without redefining them (unless this option is specified), you need notspecify rfc1155.asn1 on the command line.

-bInstructs the compiler to include CMIP descriptions in GDMO behaviorclauses. Normally, a reference to the description of the Concise MIB object isgiven in the GDMO output. By specifying -b , the description is copied tothe Behavior clause of the GDMO managed object class or attribute.

-dDisplays debugging information during translation.

-hPrints the usage message.

-lInstructs the compiler to generate only a GDMO output file and an ASN.1type file for the last specified Concise MIB file. This is useful if a MIBimports information from another MIB, but you wish to translate only the

hostname% em_cmib2gdmo [ -1155 -b -d -h -l -t -w ] <file>...


3

MIB with the dependency. For example, if the (RMON) MIB rfc1271imports OIDs from rfc1213 (MIB-II), but you have no desire to translaterfc1213 , you can use the following command:

Only the rfc1271.gdmo and rfc1271TYPE.asn1 output files aregenerated.

-tDo not perform typechecking. By default, the translator performs variouschecks to ensure that the Concise MIB definition is complete andmeaningful. This includes ensuring that the syntax types of table entriesmatch the variables declared in the table entry, validating that all referenceidentifier names and types are defined, and checking that the form of theConcise MIB definition is correct (e.g. table entries are defined within tables,etc.). If you specified -t , these checks are skipped. Note that in both cases,the output files are still generated.

-wDo not print warnings. Several potential problems discovered duringtranslation are not serious enough to be considered errors, and are thusclassified as warnings.

<file1> <file2>Specifies the names of the Concise MIB files to be compiled.

3.4.3 See Also

For detailed information about Concise MIBs and the format of Concise MIBdefinitions, refer to the following reference materials:

• RFC 1212, Concise MIB Definitions

• RFC 1215, A Convention for Defining Traps for use with the SNMP

• LaBarre, Lee (Ed), ISO/CCITT and Internet Management Coexistence (IIMC):Translation of Internet MIBs to ISO/CCITT GDMO MIBs, March 26, 1993

• LaBarre, Lee (Ed), ISO/CCITT and Internet Management Coexistence (IIMC):Translation of Internet MIB-II (RFC1213) to ISO/CCITT GDMO MIB

• ISO/CCITT SMI Guidelines for Definition of Managed Objects [ISO10165-4]

hostname% em_cmib2gdmo -l rfc1213.mib rfc1271.mib

Compilers 3-15

3

3.4.4 Diagnostics

The compiler is structured to recover from syntax errors. The type checker doesnot affect the translation process, but simply produces messages if it finds typeerrors. The GDMO output phase prints warnings for those OIDs that are notresolved. It also prints the characters ??? in place of the unresolved OID in theGDMO output file.

3.5 The Schema CompilerThe SunNet Manager (SNM) 2.x products use schema files to represent themanaged object classes available to the SNM database. You must use theSchema compiler (em_snm2gdmo) as the first step in converting the SNM 2.2or later schema files into GDMO descriptions used in Solstice EM.

To translate an SNM 2.2 or later schema file, run the Schema compiler with thefile to be translated as an argument (<filename>). The output of the translationproduces two files:

• A GDMO document with a name of the form <filename>.gdmo for non-agentschemas, or <agent/proxy_name>.gdmo for SNM agent schemas.

• An ASN.1 document with a name of the form <filename>.asn1 for non-agentschemas, or <agent/proxy_name>.asn1 for SNM agent schemas.

These output files are created in the directory from which you invoke theSchema compiler. Once you have created the output files, you must then passthem through the GDMO compiler.

3.5.1 em_snm2gdmo Command Line Syntax

Invoke the Schema compiler from the command line as follows:

You must specify the <filename> of the schema file you want to translate, andany unused <OID_branch> number for that file. This number is used to assigna unique OID to every record type defined within the specified schema file. To

hostname% em_snm2gdmo <filename> < OID_branch>


3

determine which OID branch numbers have not already been used, go to thedirectory where the ASN.1 documents are stored (the default directory is$EM_HOME/etc/asn1 ), then type the following command:

All files that are generated by the schema compiler will contain the line:

The OID branch numbers “0” and “1” are already reserved:

• “0” is reserved for SNM agent/proxy schemas, which can be found in$SNM_HOME/agents.

• “1” is reserved specifically for the schema file elements.schema .

To find out what other OID branch numbers have already been used, edit thefiles listed as a result of the grep command shown above. Table 3-2 lists is thecontents of the file cooptoolsschema.asn1 .

hostname% grep “em_snm2gdmo” *.asn1

-- This file was generated by em_snm2gdmo.

Table 3-2 cooptoolsschema.asn1 file

-- This file was generated by em_snm2gdmo.

-- The module name is used by the 2.x compatibility library.

-- Do not edit this file by hand.

CooptoolsschemaASN1 { iso(1) org(3) dod(6) internet(1) private(4) enterprise(1)

sun(42) products(2) management(2) em(2) rpc(12) 3 }

DEFINITIONS ::= BEGIN

cooptoolsschemaREG OBJECT IDENTIFIER ::= { iso(1) org(3) dod(6)

internet(1) private(4) enterprise(1) sun(42)

products(2) management(2) em(2) rpc(12) 3 }

Compilers 3-17

3

The OID branch number is the last integer before the } character in the linesbeginning with “Cooptoolsschema”. The number 3 has been assigned to theschema file cooptools.schema .

3.5.2 See Also

Refer to the chapter entitled “Writing an Agent Schema” in theSite/SunNet/Domain Manager Application and Agent Development Guide for adescription of the schema file format.

3.5.3 Diagnostics

The Schema compiler stops at the first occurrence of an error in the schema file.In many cases it displays messages that aid in debugging, but does not do so inall cases.

ViewdotHoldingAreaData ::= SEQUENCE {

name RpcCommonDef.String,

contact RpcCommonDef.String,

location RpcCommonDef.String,

description RpcCommonDef.String,

glyphusrState RpcCommonDef.Enumeration

}

END

Table 3-2 cooptoolsschema.asn1 file


3

4-1

Management Protocol Support 4

4.1 IntroductionSolstice EM provides management protocol support in two ways:

• Management Protocol Adaptor (MPA)

• Protocol Driver Module (PDM)

4.1.1 Management Protocol Adaptor Overview

Solstice EM provides a Common Management Information Protocol (CMIP)MPA to provide communication services between agents of OSI managedresources and the Solstice EM MIS. Refer to Section 4.2, “CMIP MPA,” for moredetailed information. Solstice EM also provides a mechanism for creating yourown MPA to interface to a legacy protocol by using the SunNet Manager(SNM) proxy agent mechanism. Refer to Section 4.3, “Proprietary ProtocolMPA,” on page 4-8 for information about creating your own MPA.

Introduction page 4-1

CMIP MPA page 4-2

Proprietary Protocol MPA page 4-8

SNMP PDM page 4-9

RPC PDM page 4-9


4

4.1.2 Protocol Driver Module Overview

Two PDMs are provided with the Solstice EM product. The SNMP PDMprovides Simple Network Management Protocol (SNMP) managementprotocol support. The RPC PDM provides Remote Procedure Call (RPC)management protocol support. The PDMs are a component of the MIS andtherefore run on the machine where the MIS is running. Refer to Section 4.4,“SNMP PDM,” for a more detailed description of the SNMP PDM, and toSection 4.5, “RPC PDM,” for a more detailed description of the RPC PDM.

4.1.3 SNMP Version 2 Support

Solstice EM provides support for SNMP Version 2 through the SunNetManager SNMP Version 2 proxy agent na.snmpv2 . For more information,refer to the “Configuring SunNet Manager SNMP Proxy Agents” chapter in theSolstice Enterprise Manager Administration Guide.

4.2 CMIP MPAThe Solstice EM CMIP MPA provides communication services between agentsof OSI managed resources and the Solstice EM MIS. An installed Solstice EMenvironment may contain one or more CMIP MPA’s, each being a gatewaybetween the CMIP management protocol and the MIS, or a direct interface to amanaged resource (no intervening management protocol). A CMIP MPA canrun on the same host where the MIS is located or on a remote host.

The CMIP MPA translates CMIS like primitives received from the MIS via thePortable Management Interface (PMI) into CMIP messages. Each CMIP MPA isa translation interface to the CMIP management protocol and its data types.

In addition to its function as a translation interface, a CMIP MPA providesdistributed processing on behalf of the MIS.

Each CMIP MPA provides the following services:

• Translates CMIS-like MIS request messages to CMIP messages

• Translates CMIP responses to CMIS-like MIS messages

• Correlates responses to outstanding MIS requests

• Handles linked responses

Management Protocol Support 4-3

4

• Translates Event notifications to MIS messages and forwards them to theMIS

4.2.0.1 Event Notification Handling

A CMIP MPA receives asynchronous, unsolicited notifications from agents ofmanaged OSI resources, which it then forwards to a specific MIS. If a CMIPMPA is not directed to forward notifications, they will not be forwarded.Specify the MIS to receive the notifications in the EM_MIS_DEFAULT_HOSTenvironment variable. For more information see Chapter 7, “MIS to MISCommunication.”

A CMIP MPA is a Solstice EM component that allows access to managedresources via CMIP. The CMIP MPA receives management directives from theMIS and translates the directives into proper CMIP messages. In other words,the CMIP MPA is the CMIP Proxy Agent for the MIS.

4.2.1 Starting a CMIP MPA

The CMIP MPA is started by one of the following methods:

• Electing to have the CMIP MPA package (SUNWemcpa) installed during theSolstice EM installation process. The package script determines whether ornot the SunLink CMIP is installed. If it is, the script starts the CMIP MPA.

• Rebooting the machine where the CMIP MPA is located

• Executing the /etc/rc2.d/S98cmipmpa script

The MIS finds out about a CMIP MPA by the information specified in theCMIP MPA /var/SUNWconn/em/conf/EM-config configuration file. Theinformation in this file includes:

• The default machine name where the MIS is located (the default value islocalhost)

• The default port number used by the MIS to communicate to the CMIP MPA

After the CMIP MPA is initialized, it waits for incoming messages from theMIS and CMIP stack. Messages can be either requests or event notifications. Ifthe message is a request sent from the MIS, it is translated into a CMIPmessage and sent to the CMIP stack. All outstanding requests are maintainedby the CMIP MPA; when it receives a response, it correlates the response with


4

the proper outstanding request, and forwards the response to the MIS. If themessage is an event notification, it is forwarded to the MIS specified by theEM_CMIP_MPA_DEFAULT_HOST environment variable.

The CMIP MPA does not filter responses and event notifications that originatein a CMIP stack. The CMIP MPA translates all messages from the CMIP stackinto CMIS-like messages and passes them to the MIS specified in theEM_MIS_DEFAULT_HOST environment variable. Similarly, the CMIP MPA doesnot filter messages that originate in an MIS. The CMIP MPA translates theCMIS-like messages to CMIP messages and passes them to the CMIP stack.

4.2.2 Configuring a CMIP MPA

CMIP MPAs need to be configured prior to attempting to access managedresources via the CMIP protocol. Refer to the “Configuring Communicationwith CMIP Agents” chapter in the Solstice Enterprise Manager AdministrationGuide.

4.2.3 CMIP MPA and MIS Messages

This section describes the information that is available in each MIS messagereceived by the CMIP MPA and the information in a CMIP MPA messagereceived by the MIS.

4.2.3.1 GET Request

A GET request contains the following information:

• Object Class

• Object Instance

• Attribute Id list (optional)

• Filtering information (optional)

• Scoping information (optional)

4.2.3.2 GET Response

A GET response contains the following information:


4

• Object Class

• Object Instance

• Attribute list

• Linked flag—contains the value true if this is a response to a scoped requestand is not the final response.

4.2.3.3 SET Request

A SET request contains the following information:

• Object Class

• Object Instance

• Modification list—a list of attributes and their associated operation. Thevalid operations are: replace , setToDefault , addValues , andremoveValues .

• Mode—specify one of the following values: CONFIRMED or UNCONFIRMED. IfCONFIRMED mode is specified, a response is expected for this request.



4.2.3.4 SET Response

A SET response contains the following information:

• Object Class

• Object Instance

• Attribute list

• Linked flag—this field has the value true if this is a response to a scopedrequest and is not the final response.

4.2.3.5 ACTION Request

An ACTION request contains the following information:

• Object Class


4

• Object Instance

• Action type—specifies the type of action to be performed

• Action info—indicates the arguments to be used by the action (optional)

• Mode—specify one of the following values: CONFIRMED or UNCONFIRMED. IfCONFIRMED mode is specified, a response is expected for this request



4.2.3.6 ACTION Response

An ACTION response contains the following information:

• Object Class

• Object Instance

• Action type

• Action reply info—contains the result of an action (optional)

• Linked flag—contains the value true if this is a response to a scoped requestand is not the final response (optional)

4.2.3.7 CREATE Request

A CREATE request contains the following information:

• Object Class

• Object Instance—the name of the instance to be created

• Superior OI—identifies the existing managed object instance that is to be thesuperior of the new managed object instance. If this value is specified, theObject Instance value should not be supplied.

• Reference OI—specifies an existing instance of the same class as themanaged object to be created. Attribute values associated with the referenceobject instance become the default values for those not specified by theattribute list parameter (optional).


4

• Attribute list—specifies the set of attribute identifiers and values that are tobe assigned to the new instance. These values override the correspondingattributes derived from the reference object instance (optional).

4.2.3.8 CREATE Response

A CREATE response contains the following information:

• Object Class

• Object Instance

• Attribute list—this field indicates the initial values of the attributes of thenew object instance (optional)

4.2.3.9 DELETE Request

A DELETE request contains the following information:

• Object Class

• Object Instance



4.2.3.10 DELETE Response

A DELETE response contains the following information:

• Object Class

• Object Instance

• Linked flag—contains the value true if this is a response to a scoped requestand is not the final response (optional)

4.2.3.11 CANCEL-GET Request

A CANCEL-GET request contains the following information:

• Id of the GET request to be cancelled


4

4.2.3.12 CANCEL-GET Response

A CANCEL-GET response contains the following information:

• Id of the GET request that is cancelled

4.2.3.13 EVENT Request

An EVENT request contains the following information:

• Object Class

• Object Instance

• Event type—specifies the type of event

• Event info—indicates the information associated with the event (optional)

• Mode—specify one of the following values: CONFIRMED or UNCONFIRMED. IfCONFIRMED mode is specified, a response is expected for this request

• Event time—time the event was generated

4.2.3.14 EVENT Response

An EVENT response contains the following information:

• Object Class

• Object Instance

• Event type

• Event reply info—this field contains the information associated with theevent response (optional)

4.3 Proprietary Protocol MPAFor information on proprietary protocol MPAs, see the Solstice EnterpriseManager Application Development Guide.


4

4.4 SNMP PDMThe Simple Network Management Protocol (SNMP) Protocol Driver Module(PDM) allows you to communicate with SNMP for SNMP-managed devices.The SNMP PDM works as a proxy between the Solstice EM MIS (where it islocated) and any device on the network that is SNMP-manageable. This allowsyou to manage any number of Management Information Bases (MIBs), whereeither standard SNMP MIB, objects, or enterprise-specific objects can bedefined. SNMP MIBs are compiled by the Concise MIB compiler(em_cmib2gdmo) into GDMO and ASN.1 descriptions, which are then loadedinto the Solstice EM MIS. You can then send requests to the MIS that areforwarded to the SNMP PDM.

When an SNMP request is received by the Solstice EM MIS, the MIS routes aCMIS-like request to the SNMP PDM. The SNMP PDM is capable of receivingmultiple requests. When the new request arrives, the SNMP PDM translatesthe CMIS-like message into a corresponding SNMP request. It then sends therequest to the specified device and waits for a response. Upon receiving theresponse, the SNMP PDM translates the SNMP message received from thedevice into a CMIS-like message, and sends it to the MIS.

Note – SNMP traps are handled by a separate daemon (em_snm-trap ).

4.5 RPC PDMThe Remote Procedure Call (RPC) Protocol Driver Module (PDM) provides themechanism to get data and set attribute values for devices that are managed bySNM RPC-based agents. The RPC PDM works as a proxy between the SolsticeEM MIS and any device on the network that has SNM RPC agents installed.

The RPC PDM serves a major role in providing compatibility with SunNetManager (SNM) 2.2 or later products. Agents that were written for SNM 2.2 orlater can be registered with the Solstice EM MIS, so that when a request ismade, the RPC PDM is called by the MIS to route the request via RPC calls tothe appropriate SNM agent on the appropriate host.

Note – SNM 2.2 or later schema files are compiled by the Schema compiler(em_snm2gdmo) into GDMO descriptions, which are then get loaded into theSolstice EM MIS.


4

When an RPC request is received by the Solstice EM MIS, the MIS routes therequest to the RPC PDM. When the new request arrives from an MIS, the RPCPDM translates the CMIS-like message it receives into a corresponding RPCrequest. It then sends the request to the specified SNM agent on the specifieddevice and waits for a response. Upon receiving a response from the SNMagent, the RPC PDM translates the RPC message into a CMIS-like message,and sends it to the MIS.

All communication between the MIS and the RPC PDM is CMIS-like. Allcommunication between the RPC PDM and the manageable SNM agentsoccurs via RPC. The RPC PDM appears to the SNM agent as the SNM 2.2Console does.

5-1

Log Management 5

This chapter discusses the Solstice EM logging services. MIS support systemManagement Log control functions are specified in CCITT Rec. X.735 |ISO/IEC 10164-6.

Solstice Enterprise Manager’s log management involves three main activities:

1. MIS logging—the MIS receives, processes, and stores events as log recordsin the Management Information Tree (MIT). These log records can beretrieved, updated, or purged by the Alarm Manager via PMI.

2. Historical logging—the MIS historical log files store all the event log recordsgenerated during MIS event processing and logging.

3. Historical relational database (RDB) logging—the historical log files aremapped and translated into a relational database.

These activities are illustrated in Figure 5-1.

MIS Logging page 5-2

Historical Logging page 5-6

Historical Relational Database (RDB) Logging page 5-8

Miscellaneous Processing of Database Records page 5-26


5

Figure 5-1 Log Management Process

5.1 MIS LoggingUsing the Log Manager, a log object can be created to capture specific MISevents. The discriminator construct of the log object specifies the type of eventthat is captured. Captured events become log records, which can bemanipulated by the Alarm Manager.

5.1.1 MIS Logging Services Provided

Solstice EM provides logging services that allow applications to define logobjects in the OmniPoint 1 log format1, to specify the kinds of events to belogged, and to manipulate the log records.

1. Specified in Network Management Forum: Forum 006, Forum Library - Volume 4: OMNIPoint 1Definitions, 1992.

MIS

HistoricalLog Files

RDBMSdaemon RDBMS

Oracle, Sybase,Informix, etc.

em_logmgr

DBM

PMI

em_alarmmgr

Log Management 5-3

5

Each log object contains attributes that distinguish it from other log objects.These attributes are described in Table 5-1.

Log objects can be created, modified, or deleted, just like any other managedobjects, through the Portable Management Interface (PMI). For users, the LogManager application offers the same functions available through the PortableManagement Interface (PMI).

Table 5-1 Log Object Attributes

Attribute Name Description

Name Each log object is identified by its Fully DistinguishedName (FDN) in the Solstice EM MIS’s ManagementInformation Tree (MIT).

discriminatorConstruct A test that decides whether to log an arriving notification(test can be modified).

maxLogSize Each log object has a maximum size and an attribute thatindicates when its maximum size has been reached. Amaximum size set to zero indicates no limit. Size isexpressed in octets (size can be modified).

currentLogSize Number of octets the log object and its records now occupyin the MIS (reportable but not an attribute that can bemodified).

nameBinding Specifies position of log object in the MIS’s MIT, beneaththe /system/log branch (reportable but not an attributethat can be modified).

objectClass Object class of the log object. This class is nearly alwayslog (reportable but not an attribute that can be modified).

numberOfRecords The number of log records written in the log object(reportable but not an attribute that can be modified).

logFullAction(wrap/halt)

When the log is full, it either stops accepting new records orstarts to overwrite the oldest records, according to the valueof this attribute (can be modified).

administrativeState(locked/unlocked)

When set to locked, the log object cannot be written to.When set to unlocked, allows the log object to be written to(can be modified).

operationalState(enabled/disabled)

When set to enabled, the log object is “up.” When set todisabled, the log object is “down” (reportable but not anattribute that can be modified).


5

When a log object is deleted, all of the log records stored under that log objectare also deleted. Log records are added to the log object when all of thefollowing conditions are met:

• The notification passed the test of the discriminator construct for the logobject.

• The maxLogSize has not been reached.

• The administrativeState is unlocked.

• The operationalState is enabled.

Log records are created only when an event notification is logged a log object.The contents of a log record cannot be modified.

Log records can only be deleted by the Alarm Manager. Log records aredeleted automatically when the log object it is associated with has beendeleted, or, possibly, as a consequence of the log full action. If the log fullaction is “wrap”, an individual log record will be deleted from the beginningof a log object when a new record is added.

Caution – Log records that are dropped or deleted due to the log full actioncan not be retrieved through the PMI since they no longer exist in the MIS.

5.1.2 Alarm Logging

In general, events in the MIS are not persistent. That is, they exist for the use ofSolstice EM applications only while the MIS is running. However, an event canbe defined so that it has persistence, as described below:

1. In the Log Manager, create a discriminator construct for an existing or newlog object that causes events of a given type to be logged.

2. Specify a mapping from an event object type to a log record type.

When the MIS receives an event of a type that fits the criteria of a discriminatorconstruct, the MIS logs the event in a log record of the type specified in themapping for that event type.

For more information and examples on defining a discriminator construct, seeSection 13.3, “Defining the Discriminator Construct,” in Chapter 13, “LogManager.”

Log Management 5-5

5

Alarms are a particular type of event indicating an abnormal condition. Bydefault, Solstice EM logs all alarms, which means that the default discriminatorconstruct accepts alarm events. In Solstice EM, alarms are events that have“special” characteristics and receive special treatment:

• They are logged (which would be true for any event type that fits thecriteria of a Log Manager discriminator construct and has a mapping to alog record type).

• They have attributes that allow them to be acknowledged and cleared.

• They are recognized by and displayed in the Solstice EM Alarm Managerapplication.

The default alarm types supported by Solstice EM and the log record types towhich they are mapped are listed in Table 5-2.

Table 5-2 Default Alarm Types and Log Record Types

Alarm Type Log Record Type

attributeValueChange attributeValueChangeRecord

communicationsAlarm emAlarmRecord

environmentalAlarm emAlarmRecord

equipmentAlarm emAlarmRecord

integrityViolation securityAlarmReportRecord

objectCreation objectCreationrecord

objectDeletion objectDeletionRecord

operationalViolation securityAlarmReportRecord

physicalViolation securityAlarmReportRecord

processingErrorAlarm emAlarmRecord

qualityofServiceAlarm emAlarmRecord

relationshipChange relationshipChangeRecord

securityServiceorMechanismViolation securityAlarmReportRecord

stateChange stateChangeRecord

timeDomainViolation securityAlarmReportRecord


5

The mapping shown above is defined in the file init_platform , and storedby default in $EM_HOME/install/em_platform . The mappings areimplemented by the object event2ObjectClass , whose FDN issubsystemId=”EM-MIS”/listname=”event2ObjectClass” .

Solstice EM allows you to define new alarm object types based on existingGDMO and ASN.1 definitions of alarm types. New alarm object types arecreated in the same way as you create any object type.

All alarm log records, including emInternetAlarmRecord andnerveCenterAlarmRecord , are derived from emAlarmRecord .

Collectively the standard log object and Solstice EM-specific log object typeshave a richness of functionality that will accommodate most alarm-loggingneeds. To establish a mapping at runtime, use the Object Editor to editevr2oclist . If you want the mapping to be persistent, edit theinit_platform file, then restart the MIS.

5.2 Historical LoggingHistorical logging is an extension of MIS logging in the sense that every logrecord will be kept in a historical log, and there is no log size limitation thatforces old logs to be removed. The purpose of historical logging is to providestatistics of log records over a long period of time, which MIS logging cannotsupport.

During the historical logging process, the MIS stores each log record in ahistorical log file. Each event that is logged in the persistence store is alsologged in a historical log file. The historical log file can contain many eventlogs or records.

5.2.1 Enabling Historical Logging

The environmental variable EM_HLOG_INTERVAL defines the rate (in hours)at which the historical log file is created in EM_HLOG_DIR (default is/var/opt/SUNWconn/em/data/HLOG ). If the value of EM_HLOG_INTERVAL

internetAlarm emInternetAlarmRecord

nerveCenterAlarm nerveCenterAlarmRecord

Alarm Type Log Record Type

Log Management 5-7

5

is 0 (default), then the historical log files are not created. You must setEM_HLOG_INTERVAL to a positive value by using the following series ofcommands:

Specify a positive integer in place of <number_of_hours> in the commandshown above.

5.2.2 Historical Log File Format

Historical log files contain many event log records. Each logical event logrecord contains information that describes the event. Logical event log recordsare separated by a blank line.

Unless specified otherwise, historical log files are located in the directoryspecified by the EM_HLOG_DIR environment variable (the default is/var/opt/SUNWconn/em/data/HLOG .). The naming convention forhistorical log files is:

<logID>.yymmddhh

Different types of log record events (for example, alarmRecord andobjectCreationRecord ) have a set of common attributes. These attributesare derived from the eventLog . Each log record contains a description thatincludes the type of event, where the event occurred, etc., and can be manylines in length. Each description field is separated by a delimiter ::. Theoptional fields appear at the end of the record, or as attribute value pairs.

Code Example 5-1 Generic Log Record Format

logID::logRecordId::logRecordClass::eventType::loggingTime::eventTime<RETURN>

managedObjectClass::managedObjectInstance <RETURN>

Optional attribute1=Opt-value1<RETURN>

Optional attribute2=Opt-value2<RETURN>

...

Specific attribute1=Spe-value1<RETURN>

# em_services -s# setenv EM_HLOG_INTERVAL < number_of_hours># em_services


5

Specific attribute2=Spe-value2<RETURN>

...

The example above illustrates one description of a log record. Each descriptionis separated by a blank line or carriage return (<RETURN>).

Note – New line characters are explicitly shown when present and theeventTime field is optional.

Code Example 5-2 Sample Log Record of alarmRecord Type

TestLog::2::alarmRecord::communicationsAlarm::19950124135508::19950124135508<RETURN>

system::/systemId=name:”mutley”<RETURN>

probableCause = localValue : 16<RETURN>

perceivedSeverity = minor<RETURN>

5.3 Historical Relational Database (RDB) LoggingHistorical log files store all the log record events. These historical log files areread by the em_log2rdb daemon process and its information is stored in arelational database. The em_log2rdb daemon loads the historical log fileinformation in batch mode. The process by which the information in thehistorical log files is read, translated, and transferred to a relational database(RDB) is called historical RDB logging.

Figure 5-2 Historical RDB Logging

HistoricalLog Files

RDBMSdaemon

em_log2rdb

RDBMS

Oracle, Sybase,Informix, etc.

Log Management 5-9

5

When engaging in historical RDB logging, information is retrieved from thefollowing types of files:

• Historical log files—for the raw information to be added to the databasetables

• Configuration file—for information about the database (server, user ID,password, database name, etc.)

• Database schema definition file—for information about how the log recorddescription map to database table structures

At this point, the database tables are synchronized with the historical log file tostart or continue processing the historical log file information.

After historical log file processing is complete, em_log2rdb sleeps for apredetermined period of time, after which it checks for more data to beprocessed. The cycle of sleeping, checking, and processing continues until theem_log2rdb daemon is signaled to terminate.

5.3.1 Configuration File

Information such as the type of database, server name, user name, andpassword is required to connect to a database. All of these parameters arelocated in a configuration file that overrides default locations and file names.In addition, specification of this information via the command line overridesthe configuration file information.

Note – If the em_log2rdb daemon is unable to connect to the database, Stderris notified and the process is terminated.

The default configuration file is named em_log2rdb.cfg and is located in$EM_RUNTIME/conf/ where the $EM_RUNTIME default is/var/opt/SUNWconn/em .

The configuration file contains the following information:

• DBTYPE <dbtype> (such as Sybase, Oracle, Informix, etc.)

• SERVER <server_name>

• USER <user_name>

• DATABASE <database_name>


5

• SCHEMA <schema_definition_file_name>

• HISTORYFILEPATH <historical_log_file_path>

• SLEEP <time_in_seconds>

• PASSWORD <user_password>

• comments that are preceded by “//”

Note – The default configuration location and file name can be overridden byproviding these as parameters on the command line.

5.3.2 Database Schema Definition File

In order to map the event information in the historical log files tocorresponding database tables, a database schema definition file is accessed.This definition file contains information such as how the database table isstructured and how the log record description maps or relates to the tables.After the mapping or translating is complete, the database tables are updatedwith log record information.

The default database schema definition file is named em_log2rdb.def and islocated in $EM_RUNTIME/conf/ where the $EM_RUNTIME default is/var/opt/SUNWconn/em .

Note – The definition file location and file name can be modified in theconfiguration file.

Code Example 5-3 Generic Schema Definition File

RECORD <name of the record type> (attribute-1 data-type(length),...attribute-1 data-type(length))

Log Management 5-11

5

The schema definition file in Code Example 5-5 shows the file definitions forthe Enterprise Manager em_log2rdb daemon.

Code Example 5-4 Sample Schema Definition File

RECORD event_log ({logID VARCHAR REQUIRED,logRecordId INT REQUIRED,logRecordClass VARCHAR(60) REQUIRED,eventType VARCHAR(40) REQUIRED,loggingTime DATETIME REQUIRED,eventTime DATETIME,}{managedObjectClass VARCHAR(60) REQUIRED,managedObjectInstance VARCHAR(60) REQUIRED,}notificationIdentifier INT,correlatedNotificaitons VARCHAR(60),additionalText VARCHAR,additionalInformation VARCHAR,}

Code Example 5-5 Schema Definition File for em_log2rdb Daemon

// This file contains file definitions for em_log2rdb//// The first Record definition must be eventLog and it must contain// logRecordId field. All other record definitions will implicitly// contain a log record type field, along with two other key fields// relating that record to it’s parent

// Primary RecordsRECORD eventLog ({ //block ( nl delimited ) fixed pos fldslogId string(60) REQ,logRecordId int REQ,logRecordClass string(60) REQ,eventType string(60) REQ,loggingTime datetime REQ,eventTime datetime}{managedObjectClass string(60) REQ,managedObjectInstance string REQ


5

}notificationIdentifier int,correlatedNotifications string(1024),additionalText string(1024),additionalInformation string(1024))

// The following DEFN definitions must be included in order to process// union and setof field types

// Base Defn recordsDEFN emString ({atext string(1024)})

DEFN emInt ({aint int})

DEFN emDate ({aDatetime datetime})

DEFN emSetof (ttype int)

// default Defn structuresDEFN emAttrValChgDef (attributeID string(1024) REQ,oldAttributeValue string(1024) REQ,newAttributeValue string(1024) REQ)

// Record definitionsRECORD objectCreationRecord (soureceIndicator string(40),attributeIdentifierList string(1024) // actually setof attributeId)

RECORD objectDeletionRecord (soureceIndicator string(40),attributeIdentifierList string(1024) // actually setof attributeId)


Log Management 5-13

5

RECORD emAlarmRecord (probableCause string REQ,perceivedSeverity string(20) REQ,specificProblems string(1024),backedUpStatus bool,backUpObject string(1024),trendIndication string(20),thresholdInfo string(1024),stateChangeDefinition DREF(emAttrValChgDef),monitoredAttributes string(1024),proposedRepairActions string(1024),ackState string(10),ackTime datetime,ackOperator string(60),ackText string(1024),clearState string(10),clearTime datetime,clearOperator string(60),clearText string(1024),displayState string(12),displayTime datetime,displayOperator string(60),displayText string(1024))

RECORD attributeValueChangeRecord (attributeValueChangeDefinition setof(emAttrValChgDef) REQ,sourceIndicator string(30),// attributeIdentifierList stringattributeIdentifierList setof(emString))

RECORD relationshipChangeRecord (recordChangeDefinition string(1024) REQ,sourceIndicator string(30),attributeIdentifierList setof(emString))

RECORD emInternetAlarmRecord (probableCause string,attributeIdentifierList string(1024),objectInstanceList string(1024),ackState string(10),



5

ackTime datetime,ackOperator string(60),ackText string(1024),clearState string(10),clearTime datetime,clearOperator string(60),clearText string(1024),displayState string(12),displayTime datetime,displayOperator string(60),displayText string(1024),accessControlInfo string(1024),snmpVarBindList string(1024),transportDomain string(1024),transportAddress string(1024))

RECORD nerveCenterAlarmRecord (probableCause string,perceivedSeverity string(20),specificProblems string(1024),backedUpStatus bool,backUpObject string(1024),trendIndication string(20),thresholdInfo string(1024),stateChangeDefinition DREF(emAttrValChgDef),monitoredAttributes string(1024),proposedRepairActions string(1024),ackState string(10),ackTime datetime,ackOperator string(60),ackText string(1024),clearState string(10),clearTime datetime,clearOperator string(60),clearText string(1024),displayState string(12),displayTime datetime,displayOperator string(60),displayText string(1024),mosiSeverity int,mosiStateID int)


Log Management 5-15

5

5.3.2.1 Database Schema Mapping

Common attributes of eventLog are stored in a single table named eventLog .One table is defined for storing specific attributes of any one class of records.These records are related to the eventLog with a key made up oflogID(coded)+logRecordId. Coded logID is a number assigned by theem_log2rdb daemon and can be found in Solstice EM tables.

For each log record of a known type, one record is created in the eventLogtable and one is created in the corresponding table of that type. InCode Example 5-5, probable cause and perceived severity fields are stored inemAlarmRecord table, while all other common fields are stored in eventLogtable.

Special handling is provided for lists of common items. Each list, called aSETOF, is delimited in the log history records by {} and stored in a separatetable, the structure of which corresponds to the fields in the list.

For every attribute that is present, a record is created in a table structured tohold lists of changes.

Below is an entity relationship (ER) diagram for the log record database. Aninternal primary key em_this_rn and an internal foreign key em_key_rn areused to relate the common part of a log record with its type-specificinformation.


5

Figure 5-3 Entity Relationship Model for Log Record Database

Table 5-3 lists all the log records supported by the platform.

Table 5-3 Log Record Type

Log Record Type

attributeValueChangeRecord

emAlarmRecord

objectCreationRecord

objectDeletionRecord

relationshipChangeRecord

eventLogem_this_rn

emAlarmRecordem_this_rn


emSetofem_this_rn

em_key_rn

emDateem_this_rn

em_key_rn......

...

...

...

emString

em_this_rn

em_key_rn...

emIntem_this_rn

em_key_rn...

em_this_rn

Log Management 5-17

5

5.3.2.2 Database Tables

Table 5-4 lists the tables created by the em_log2rdb daemon. The tables thatare created are specified in the configuration file. These tables correspond tothe log record types and contain miscellaneous system information.

Two additional tables are created for special functions: emTable to contain amaster list of tables and emLogHist to contain information used for trackingprocessed log history files.

stateChangeRecord

emInternetAlarmRecord

nerveCenterAlarmRecord

Table 5-4 Database Tables

Table Name

eventLog

emString

emInt

emDate

emSetof

emAttrValChgDef


objectDeletionRecord

emAlarmRecord

attributeValueChangeRecord

relationshipChangeRecord

emInternetAlarmRecord

nerveCenterAlarmRecord

Table 5-3 Log Record Type

Log Record Type


5

In the emTable table, each table entry has a table ID, which is stored in theTBLID column. For a table that stores log records, its table ID starts from 1. Fora table that stores elements of a setof attribute, its table ID starts at 1001. Forsuch entries, the table ID is used in place of its attributes value in the logrecord table.

Shown below is an example of the contents of emTable :

Below is a sample attributeValueChangeRecord table.

Table 5-5 Sample emTable

TBLNAME TBLID

emString 1001

emInt 1002

emDate 1003

emSetof 1004

emAttrValChgDef 1005

eventLog 1

objectCreationRecord 2

objectDeletionRecord 3

emAlarmRecord 4

attrubuteValueChangeRecord 5

securityAlarmReportRecord 6

relationshipChangeRecord 7

emInternetAlarmRecord 8

nerveCenterAlarmRecord 9

Table 5-6 Sample attributeValueChangeRecord Table

em_this_rn attributeValueChangeDefinition Source Indicator attributeIdentifierList

3 1005 managementOperation 1001




Log Management 5-19

5

The arrtibuteValueChangeRecord table has two setOf columns: theattributeValueChangeDefinition column and theattributeIdentifierList column. The elements for theattributeValueChangeDefinition column are stored in theemAttrValChgDef table, so 1005 is stored as the value of this column bylooking up Table 5-5. For this reason, 1001 is stored as the value for theattributeIdentifierList column, since its elements are strings. Therelationship between the each element and its owner record is stored in theemSetof table. For more information, see Figure 5-3.

The following tables illustrate specific system information for the databasetables that are created by the em_log2rdb daemon.









Table 5-7 eventLog Table

Name of the fieldMandatory /Optional

Type ofthe field

Length ofthe field Comments

em_This_Rn Mandatory int 4 Primary Key

logID Mandatory varchar < 255 Key Field (for example, “AlarmLog”)

logRecordId Mandatory int 4 Key Field (for example, “1”)

logRecordClass Mandatory varchar < 255 For example, “objectCreationRecord”

eventType Mandatory varchar < 255 For example, “objectCreation”

loggingTime Mandatory time “yyyymmddhhmmss” format in the logfile

Table 5-6 Sample attributeValueChangeRecord Table

em_this_rn attributeValueChangeDefinition Source Indicator attributeIdentifierList


5

managedObjectClass Mandatory varchar < 255 For example, “emApplicationInstance”

managedObjectInstance Mandatory varchar < 255 For example, ‘/systemId=”vidhi”’

eventTime optional time “yyyymmddhhmmss” format on file

notificationIdentifier optional int 4

correlatedNotifications optional varchar < 255

additionalText optional varchar < 255

additionalInformation optional varchar < 255

Table 5-8 objectCreationRecord Table


Type ofthe field



sourceIndicator Optional char 1 ‘1’=resourceOperation,‘2’=managementOperation,‘3’=unknown

attributeIdentifierList Optional boolean 1 SET OF AttributeId*

Table 5-9 objectDeletionRecord Table


Type ofthe field

Lengthof thefield Comments



attributeList Optional boolean 1 SET OF Attribute (See Note onpage 5-24)

Table 5-7 eventLog Table


Type ofthe field


Log Management 5-21

5

Table 5-10 emAlarmRecord Table


Type ofthe field



probableCause Mandatory varchar < 255 Choice syntax in dmi.asn1

perceivedSeverity Mandatory char 1 ‘1’=indeterminate, ‘2’=critical, ‘3’=major,‘4’=minor, ‘5’=warning, ‘6’=cleared

specificProblems Optional varchar < 255 Optional of alarmRecord

backedUpStatus Optional boolean 1 Optional of alarmRecord

backUpObject Optional varchar < 255 Object instance

trendIndication Optional char 1 ‘1’=lessSevere, ‘2’=noChange,‘3’= moreSevere

thresholdInfo Optional varchar < 255

stateChangeDefinition Optional boolean 1 Type avChangeDefinition (See Note onpage 5-24)

monitoredAttributes Optional varchar < 255

proposedRepairActions Optional varchar < 255

ackState Mandatory char 1 ‘1’=unAcked, ‘2’=acked

ackTime Mandatory time

ackOperator Mandatory varchar

ackText Mandatory varchar < 255

clearState Mandatory char 1 ‘1’=unCleared, ‘2’=cleared

clearTime Mandatory time

clearOperator Mandatory varchar < 255

clearText Mandatory varchar < 255

displayState Mandatory char 1 ‘1’=unDisplayed,‘2’=displayed

displayTime Mandatory time

displayOperator Mandatory varchar < 255

displayText Mandatory varchar < 255


5

Table 5-11 attributeValueChangeRecord Table


Type ofthe field



avChangeDefinition Mandatory boolean 1 See Note on page 5-24


attributeIdentifierList Optional boolean 1 SET OF AttributeId (See Note onpage 5-24)

Table 5-12 relationshipChangeRecord Table

Name of the fieldMandatory/ Optional

Type ofthe field



rcChangeDefinition Mandatory varchar < 255 avChangeDefinition (See Note onpage 5-24)


attributeIdentifierList Optional boolean 1 SET OF AttributeId (See Note onpage 5-24)

Table 5-13 emInternetAlarmRecord Table


Type ofthe field





Log Management 5-23

5

ackOperator Mandatory varchar < 255









displayText Mandatory varchar < 255

probableCause Mandatory varchar < 255

attributeIdentifierList Optional boolean 1 See Note on page 5-24

objectInstanceList Optional boolean 1 See Note on page 5-24

Table 5-14 nerveCenterAlarmRecord Table


Type ofthe field



probableCause Mandatory varchar < 255

perceivedSeverity Mandatory char 1 ‘1’=indeterminate, ‘2’=critical,‘3’=major, ‘4’=minor, ‘5’=warning,‘6’=cleared

specificProblems Optional varchar < 255 An optional alarmRecord

backedUpStatus Optional char 1 All fields of em_alarm_rec start

backUpObject Optional varchar < 255

Table 5-13 emInternetAlarmRecord Table


Type ofthe field



5

Note – All these attributes are of list type. These attributes are optional fieldsin the database table.

trendIndication Optional char 1 ‘1’=lessSevere, ‘2’=noChange,‘3’= moreSevere

thresholdInfo Optional varchar < 255

stateChangeDefinition Optional boolean 1 avChangeDefinition (See Note onpage 5-24)

monitoredAttributes Optional varchar < 255 See Note on page 5-24

proposedRepairActions Optional varchar < 255



ackOperator Mandatory varchar < 255









displayText Mandatory varchar < 255 All fields of em_alarm_rec end

mosiSeverity Mandatory int 4

mosiStateID Mandatory int 4

Table 5-14 nerveCenterAlarmRecord Table


Type ofthe field


Log Management 5-25

5

5.3.2.3 Database Schema Parser

Log records are derived from eventLog . Additionally, new types of logrecords can be defined by deriving from the base eventLog and adding newattributes. This allows the database structure to be configurable. Therefore, amechanism exists that facilitates dynamic addition to the known types of eventrecords by using a description language to define all record types and theirstructure. An initialization file containing these descriptions is processed eachtime the daemon is started; it must contain a definition of the base record andall other possible records. If it is determined that database tablescorresponding to each record type do not already exist, then they are created; itis possible to set a configuration option that will cause the system to failinstead.

Along with the basic data types (such as int and string ), the more complexSETOF data type is supported. The SETOF attribute type is a list. If N elementsare present in one instance of such an attribute type, then N elements arecreated in a table, emSetof , which corresponds to the list structure. (This tableis defined in a similar fashion as a record.) On encountering a data element set,a record is written to the emSetof table in addition to the actual data beingwritten to its corresponding table.

5.3.3 Starting the em_log2rdb Daemon

The em_log2rdb daemon is a Unix process that converts the Solstice EMhistorical log files to relational database tables.

To start the em_log2rdb daemon, issue the following from the command line:

hostname% em_log2rdb.< database> [-std] [-c < config_file>]


5

The <.database> parameter is the extension implemented for one of threedatabases: Sybase, Oracle, and Informix. For these three databases, theem_log2rdb .<database> commands are em_log2rdb.sybs ,em_log2rdb.orcl , and em_log2rdb.ifmx , respectively. The optionalparameters for the em_log2rdb.<database> command are described below.

5.4 Miscellaneous Processing of Database Records

5.4.1 Starting Two em_log2rdb Daemons andLogging the Records to Two Databases

To start two em_log2rdb daemons, you must provide one log2rdb.cfg filefor each daemon. The em_log2rdb daemon will check out$EM_RUNTIME/conf/log2rdb.cfg to obtain connection information to theRelational Database Management System (RDBMS). By default, theEM_RUNTIME environment variable is set to /var/opt/SUNWconn/em .

It is suggested that you create the /var/opt/SUNWconn/log2rdb_< server>file, where <server> is the name of the RDBMS, and set the EM_RUNTIMEenvironment variable to/var/opt/SUNWconn/log2rdb_< server>. Using thisapproach, you can start any number of em_log2rdb daemons and have thempopulate their own RDBMSs with log records. The historical log files cannot beremoved until they are all read by the em_log2rdb daemons you started. Eachem_log2rdb daemon keeps synchronization information within its ownRDBMS.

Option Description

-help Print list of options (with descriptions) for theem_log2rdb.< database> command.

-s Instructs the daemon to terminate the processing ofhistorical log files after one pass through

-t Trace the SQL.

-d Drop all existing database tables.

-c < config_file> Specify the configuration file name. This will override thedefault configuration file.

Log Management 5-27

5

Note – Instead of starting multiple em_log2rdb daemons, you can use thefacility provided by the database server to achieve the same result. Forexample, you can use the replication feature of an Oracle server to replicate thelog records from one server to as many servers as needed.

5.4.2 Storing Different Types of emAlarmRecord inDifferent Databases

By using the insert trigger provided by RDBMS servers, it is possible to detectthe type of an emAlarmRecord and move it from one table to a different tablein a different database. Detailed implementation of such a trigger depends onthe provision of the individual RDBMS. Refer to the corresponding databasemanual(s) for more information.

5.4.3 Report Generation

It is possible to create a view that merges log records of the same type fromvarious databases so that the report tool can use the view to generate a report.It is not necessary to change the current implementation of the em_log2rdbdaemon in order to achieve this goal. For example, suppose the log recordsfrom MIS A and MIS B are stored into Oracle Server A and Oracle Server B,respectively. The following SQL statement creates a view calledemAlarmRecord that unions the alarm record table from Server A and ServerB for joint report purposes. Since the view does not contain a join, queryingthis view is just as fast as querying the underlying tables that comprise theview.

create view emAlarmRecord asselect em_this_rn, probableCause, perceivedSeverity, ... from A.emAlarmRecordunionselect em_this_rn, probableCause, perceivedSeverity, ... from B.emAlarmRecord


5

6-1

Alarm Service 6

6.1 OverviewTopology nodes are created by users to logically model managed objects intheir network management environment. This is the object that is seen by theViewer. Each topology node has an attribute topoNodeMOSet, which points tothe managed object instances (MOIs) this topology node represents. Thus, thetopology node represents the state of the managed objects or MOIs. When analarm comes into the platform, it is against the MOI, not the topology node.

The Alarm Service is the module in the MIS responsible for updating andstoring the state of MOIs in the MIS. The state of an MOI is reflected in thecolor of its corresponding topology node in the Viewer.

Overview page 6-1

Alarm Management page 6-2

The Alarm Service in Action page 6-6

Configuring the Alarm Service page 6-9

Alarm Information Display in EM Applications page 6-10

User-configurable Alarm Log Record Filter for Alarm Service page 6-12


6

When an alarm event is received by the MIS, it is stored as an alarm log record,based on the alarm log attribute discriminatorConstruct. (For more informationon discriminatorConstruct, refer to the “Log Management” and “LogManager” chapters of the Solstice Enterprise Manager Reference Manual.)

The Alarm Service is notified with the creation of each alarm log record. Itmaps the MOI value to the corresponding topology node and updates thealarm counters based on severity. This triggers the severity propagation oftopoNode in two ways:

1. Propagates to parents, according to the attribute topoNodeParents (you canhave multiple parents). This applies if topoNodePropagateUp is set to“true.”

2. Propagates to peers, according to the attribute topoNodePropagatePeers.This applies if topoNodePropagateUp is set to “true.”

In addition, the Alarm Service keeps the topoNodeSeverity synchronized sothat it represents the highest (most critical) uncleared alarm log record that isposted against the topology node. When there are no longer any unclearedalarms posted against a topology node, the topoNodeSeverity returns to its“normal” value of cleared.

6.2 Alarm ManagementAlarms arrive at the MIS as event notifications. A log object is a software entitythat collects records (called log records) of event notifications. As many logobjects as you want can be created using the Log Manager. (For moreinformation on log objects and the Log Manager, see Chapter 5, “LogManagement,” and Chapter 13, “Log Manager.”)

Alarms have a special log object, AlarmLog, to subscribe alarm notifications.This is the default log object shipped with Solstice EM. By default, the AlarmService monitors the AlarmLog, which includes all alarm types except for thefollowing:

• attributeValueChange

• snmAlarmEvent

• objectCreation

• objectDeletion

Alarm Service 6-3

6

• stateChange

• Any alarm type without a perceivedSeverity

It is possible to modify the AlarmLog discriminator construct to:

• Log various other types of alarms to the AlarmLog

• Point the Alarm Service to another log object or multiple log objects

For information on how to do this, see the “Defining the DiscriminatorConstruct” section in Chapter 13, “Log Manager.”

Figure 6-3 illustrates how internetAlarms and other trap notifications, CMIPnotifications, and nerveCenterAlarms get logged to the AlarmLog.


6

Figure 6-1 Logging nerveCenterAlarms, CMIP notifications, and internetAlarms to theAlarmLog

Figure 6-2 illustrates how snmAlarmTraps get logged to the AlarmLog.

SNMRPC

Agents

Solstice EM MIS

NerveCenter

SNMPAgents

CMIPAgents

nerveCenterAlarm response

AlarmLog

poll

internetAlarm and other

trap notifications

CMIPNotification

response

poll

response

poll

em_snmp-trap

Alarm Service 6-5

6

Figure 6-2 Logging snmAlarmTraps to the AlarmLog

Figure 6-3 illustrates the various components that use the Alarm Service.

Solstice EM MISAlarm Log

SNM Console

SNMRPCAgent

EventDispatcher

even

tre

ques

t

CC Sender

registers

registers

EventDispatcher

CC Receiver

SNM Trap

SNM EventForwarder

(em_snmfwd)


6

Figure 6-3 Alarm Service and Components

6.3 The Alarm Service in ActionThe scenario in this section is designed to show you how the Alarm Serviceworks. You must perform this scenario on a machine where the MIS is runninglocally, and the machine must be SNMP-manageable. If it is not, you mustcreate an SNMP agent by using the Object Configuration Tool. See Chapter 19,“Object Configuration Tool,” for more information.

Solstice EM MIS

AlarmLog

Topology Nodes

LogList

Alarm Service

mon

itors

AlarmManager

clears alarmsco

ntro

ls

OBEDedits

Viewerchange icon color

sets

faul

t sta

tus

Alarm Service 6-7

6

1. Populate the MIS with your machine, if it does not already exist:

For detailed information on Discover, see Chapter 11, “Discover.”

2. Start the Alarm Manager:

For detailed information about the Alarm Manager, see Chapter 15, “AlarmManager.”

3. Start the Viewer:

For detailed information on the Viewer, see Chapter 10, “Viewer.”

4. Find your device in the viewer canvas.

In the viewer canvas, you should see a topology node that has the name ofyour machine. The topoNodeMOSet attribute of this topology node mightcontain:

where <host> is the name of your machine. This MOI represents the SNMPagent running on your machine. The topology node in the Viewer, then,represents the state of this agent running on your machine.

Alarms in the system get posted against MOIs. The Alarm Service maps theMOI to the topology node representing it. To see how this works, login asroot , then:

hostname% em_discover -device < hostname>

hostname% em_alarmmgr &

hostname% em_viewer &

/systemId=name:”< host>”/internetClassId={1 3 6 1 4 1 42 2 2 2 9 2 4 1 0}/cmipsnmpProxyAgentId=”< host>”


6

5. Kill the SNMP daemon on your machine with the following command:

6. Restart the SNMP daemon:

When the SNMP daemon is restarted, a Cold Start trap is sent by default to thelocal host. This causes a critical alarm to be posted against the MOIrepresenting the SNMP agent. The Alarm Service maps this to zero or moretopology nodes (zero or more because there may be no topology nodes withthis MOI as a member of their topoNodeMOSet, or there may be many thatcontain this MOI in their topoNodeMOSet).

When the alarm is posted, the icon color in the Viewer changes according tothe severity of the alarm. The color of the alarm in the Alarm Manager matchesthe color of the topology node in the Viewer.

7. Purge the Alarm using the Alarm Manager.Click once on the alarm in the table, then select Object ➤ Purge From Log.

The color of the icon in the Viewer should be reset.

The key to understanding the Alarm Service is to understand that a managedobject has a state. The Viewer uses icons to represent the state of the managedobjects, while the Alarm Manager shows the actual managed object. Forexample, suppose your machine has only one managed object: an SNMP agent,as in this scenario, and that there are already five critical alarms posted againstthis agent. If a sixth alarm of a severity lower than critical (minor, for example)were posted against this managed object, the Viewer would not reflect thisalarm, because of its lower severity. The Alarm Manager, however, wouldshow all six alarms.

Both the Viewer and the Alarm Manager use the same severity mapping sothat the colors are consistent.

# /etc/init.d/init.snmpd stop

# /etc/init.d/init.snmpd start

Alarm Service 6-9

6

6.4 Configuring the Alarm ServiceBy default, the Alarm Service monitors the AlarmLog. Suppose, however, thatyou want to log some non-default alarms to the AlarmLog, or want to monitoronly a specific set of alarms, and have created some additional log objects inaddition to AlarmLog. (You can create additional log objects by using the LogManager.) You can use the Object Editor (OBED) to tell the Alarm Servicewhich log(s) to monitor.

The emAlarmServiceList object has the attribute emAlarmLogList. Thisattribute, by default, contains the value AlarmLog. The Alarm Serviceautomatically monitors any log that is added to emAlarmLogList.

6.4.1 Adding Log Objects to emAlarmLogList

To add a log objects to emAlarmLogList, you must use OBED to modify theemAlarmServiceList object:

1. Click on the folder next to subsystemId=”EM_MIS” to display thisobject’s subordinates.

2. Double-click on the listname=”emAlarmServiceList” subordinateobject. This causes the Object Configuration window to appear.

3. Add the log objects you want the Alarm Service to monitor in theemAlarmLogList field.By default, the emAlarmLogList contains the following:

Suppose you have created a log object called WarningLog. To add this log toemAlarmLogList, change the emAlarmLogList field as follows:

As many log objects as you want may be added in this fashion. Just be sureto separate each one with a comma.

4. Click on the Update button when you are finished.

{ string : "AlarmLog" }

{ string : "AlarmLog", string : ”WarningLog” }


6

6.4.2 Deleting Log Objects from emAlarmLogList

If you do not want the Alarm Service to monitor a specific log object, the logobject must be removed from emAlarmLogList. You can remove a log object byusing the Log Manager or OBED.

To remove a log object using the Log Manager:

1. Select the log(s) you want to delete in the Log Manager main window.

2. Select Edit ➤ Delete from the menu bar the delete the selected log(s).

To remove a log object using OBED:

1. Select the log(s) you want to delete in the OBED main window.Log Objects appear as a subordinate object beneath the systemId object.

2. Select Edit ➤ Delete from the menu bar the delete the selected log(s).

When you remove a log object from the MIS, it is automatically removed fromemAlarmLogList, thus eliminating the necessity of you having to manuallyedit this field in the Object Configuration window.

6.4.3 Turning Off the Alarm Service

Removing all log objects from emAlarmLoglist in effect turns off the AlarmService in the sense that it will not change the topoNodeSeverity for a topologynode. However, the Alarm Service still keeps track of the MOI-to-topoNode IDmapping, in the hopes that when a log object is re-added to emAlarmLoglist,there is no catching-up penalty.

6.5 Alarm Information Display in EM ApplicationsThe following subsections explain how the Alarm Service controls the colormapping for alarms displayed in Solstice EM applications.

6.5.1 Alarm Information Display in Alarm Manager

The Alarm Manager does not display the alarm notifications directly. Instead,it displays the alarm log records contained in the alarm logs (for example,“AlarmLog”) in a tabular format. You can specify filters to ignore unwantedalarms, association groups to summarize alarms, and sorting to prioritize

Alarm Service 6-11

6

alarms. The Alarm Manager also monitors the alarm log for objectCreation,objectDeletion, attributeValueChange, and other events for alarm log records,updating the display as necessary.

The Alarm Manager displays each row in the table in colors, based on theseverity of the alarm log record. The standard attribute used to denote severityis the perceivedSeverity attribute, which is defined in ASN.1 as one of thefollowing enumerated types: indeterminate, critical, major, minor, warning,and cleared.

The alarm record managed object classes with perceivedSeverity attributes are:

• emAlarmRecord

• emInternetAlarmRecord

• nerveCenterAlarmRecord

Severity of the alarm log record is translated to a color by the user-configurablecolor mapping defined by the Nerve Center. The default color mapping isshown below.

• Normal: no color• Warning: yellow• Minor: cyan• Major: orange• Critical: red• Indeterminate:blue

If you want to change the default color mapping, you must use the Severitieswindow in the Request Designer by selecting Edit ➤ Severities from the menubar. This change, however, is not dynamic, meaning that you cannot restart theViewer and Alarm Manager to see this change in color. For more informationabout changing the color mapping, see the “Request Designer” chapter in theSolstice Enterprise Manager Administration Guide.

6.5.2 Alarm Information Display in Viewer

The Viewer also displays alarm information, but in a more indirect and limitedway. The Viewer does not read the alarm log or wait for events for alarm logrecords, such as objectCreation or objectDeletion. The alarm information theViewer does display are updates by the Alarm Service.


6

6.6 User-configurable Alarm Log Record Filter forAlarm Service

Table 6-1 compares the user options for processing alarm log recordinformation in the Alarm Manager versus the Viewer.

The goal is for the Viewer to display alarm log information consistent with theAlarm Manager.

Table 6-1 Alarm Log Record Processing Options

Alarm LogProcessing Option Alarm Manager Viewer

Sorting By any attribute By severity

Association By object instance, event type, probablecause, specific problem, additional text,additional info identifier, andadditional information.

By object instance(topology node)

Filtering All open, cleared, or acknowledgedalarms; all within a certain time period,only certain alarms, only alarms oncertain objects, only certain severities,only certain event types, and more.

Only uncleared alarms

7-1

MIS to MIS Communication 7

7.1 OverviewThis chapter describes concepts and procedures for setting up MIS-MIScommunication. MIS-MIS communication enables you to view the objects inthe remote MIS as if they existed in your local MIS.

The following section describes the concepts and functions of MIS-MIScommunication on the EM platform.

7.1.1 MIS-MIS Communication

The central function of the EM MIS is to make data regarding managed objectsavailable to its client services. The term managed objects includes both thephysical resources connected to the network, such as a network hub or router,as well as logical entities such as routing tables or printer queues. Naming ofmanaged object instances is based on a containment relationship. Containmentcan be visualized as a directed graph with each directed edge pointing from a

Overview page 7-1

Using MIS Manager page 7-9

Configuring MIS-to-MIS Communication page 7-15

Logging Events Sent from Another MIS page 7-16


7

contained managed object to a containing managed object. Containment, asused for naming, implies a hierarchy. A managed object instance that containsanother is said to be the superior; the contained managed object instance isreferred to as the subordinate.

7.1.1.1 The Management Information Tree (MIT)

All access to managed objects is achieved through the ManagementInformation Tree (MIT). The MIT is the globally defined object naming orcontainment tree as defined in the ITU-T X.700 series of documents. Everyobject in the MIT is defined in terms of its superior object in the tree. Theultimate superior of the MIT or the top of the containment tree is the root,similar to root in the UNIX file system. All managed objects must be namedunambiguously within the framework of inter-operable management. That is,every managed object must have a name which distinguishes it from all otherobject instances in the world or global name space. The globally unique nameof any object in the MIT is its full path name from the root to where it lives inthe tree. This is defined in the ITU-T X.700 series of documents as theDistinguished Name (DN) of the object in Global Form.

The MIT or containment tree is considered to span managed systems. Whatthis means is that if all management systems in the global name space wereconnected, and a management application did a scoped request starting at theglobal root, that application would be able to see every object defined in theglobal name space. This global name space would include thousands ofmanagement systems from many different companies.

7.1.1.2 MIS Roles in MIS-MIS Communication

A management system — such as the MIS — provides services to apredetermined set of managed objects in the MIT. Since the objects for whichthe MIS provides services are a subset of the objects in the global name space,the MIS must be able to act in both a manager and an Agent role. The divisionof roles is determined by the configuration of the MIS and the requirements ofthe management framework. When a request is made for an object which isnon-local to the MIS, it is forwarded to the appropriate Agent. In this case theMIS is acting in a manager role. If the object is local to the MIS, the informationis retrieved and returned to the requester. In this case, the MIS is acting in anAgent role. The manager role is achieved by allowing the user to configure

MIS to MIS Communication 7-3

7

parts of the MIT represented by the MIS as being non-local. Thus, the requeststo that part of the MIT are forwarded to the Agent configured to manage thatpart of the tree.

MIS-MIS communication is achieved when two or more MISs are connectedand set up to forward requests for managed objects in manager and Agentroles. The MIS forwarding a request is acting in the manager role, while theMIS receiving the request is acting in the Agent role. To an application, it istransparent as to whether the object being accessed is local or non-local. TheMIS-MIS communication (MMC) between MISs make it transparent. MMC isanalogous to NFS mounting a file system. Configuring a branch of the MIT forMMC is often referred to as mounting a section of the MIT.

In the global name space, the MIS may act in a manager or Agent role tomanagement entities of other vendors. For example, when forwarding arequest for an object in the MIT, the MIS may be forwarding the request toanother OSI-conformant manager acting in an Agent role. The latter, in turn,then takes the manager role and forwards the request to another manageracting in the Agent role.

7.1.1.3 Naming Attribute and Distinguished Names

For every object class defined, there is one attribute which is defined as thenaming attribute. That attribute and its value make up what is referred to as anAttribute Value Assertion (AVA). Each managed object instance in the MIT isidentified within the scope of its superior object by means of its namingattribute AVA. When used for naming in this way, an AVA is called a relativedistinguished name (RDN). A distinguished name (DN) is a sequence of RDNsbeginning with the global root and ending with the AVA for the named objectinstance. For example, in the diagram below, the DN of the object instanceAA=1 is as follows:

The RDN is simply AA=1. Note that when naming an attribute, the global rootis never used. This is because it is defined as a NULL object and is really just astarting point for the global name space.

{{sys=A},{A=1},{AA=1}}


7

The EM platform often displays DNs in a style similar to that of a pathname toa file in the UNIX file system. Throughout the remainder of this document,distinguished names will be referenced in what is called the “slash format” fora DN. The slash format for the above example is:

7.1.1.4 Examples

This section provides various examples of MIS-MIS communication.

Accessing Objects without an MIS-MIS ConnectionFigure 7-1 shows the MITs of two MISs — A and B — which are not connected.If an application needs to model or manage objects in both MISs, it mustestablish an association (connection via the PMI) to both MIS A and MIS Bsimultaneously. When accessing an object on MIS A and MIS B, the applicationmust do so over two separate associations. This is not of major significanceunless you consider an application which may be managing thousands ofobjects spread over 20 MISs. The application must keep track of 20simultaneous associations, and which objects are accessed over whichassociations.

Figure 7-1 MITs of Two Unconnected MISs

/sys=A/A=1/AA=1

sys=A

A=1 A=2

AA=1 AA=2 AA=3

B=1

BB=1

Root Root


7

Accessing Objects over MIS-MIS ConnectionsFigure 7-2 shows the same two MISs with A acting in the manager role and Bacting in the Agent role. When an application connected to A accesses anyobject with the first RDN equal to /sys=B, such as the object /sys=B/B=1/BB=1, the request is forwarded by MIS A to MIS B. The first RDN in the DNis used to decide whether the request is local or remote. If the object/sys=A/A=2 is accessed, MIS A acts in the Agent role and returns the localobject. To the application, access to the object on MIS A or B is transparent. It isonly aware that it has retrieved two objects with DNs. The MIS, based on thefirst RDN of the requested DN, determines where the object actually resides.

In the diagram below, it would be possible for MIS B to mount MIS A into itsMIT so that whether the application is connected to MIS A or B it will bepresented with the same set of objects.

Figure 7-2 MITs of Two Connected MISs

sys=A

A=1 A=2

AA=1 AA=2 AA=3

Root

B=1

BB=1

Root

sys=Bsys=B


7

Figure 7-2, above, presents a very simple usage of MMC. An advantage toMMC is that it allows the user to configure their network management into ahierarchical management scheme. For example, suppose a company has abuilding with three physical networks (Figure 7-3). There is one operator incharge of the overall configuration, one operator in charge of all the networksin the building, and one operator in charge of each individual net. Assumingthat each MIS is a box and a circle represents an operator, the followingconfiguration may be achieved using MMC. Note that an arrow going fromone MIS to another dictates a manager Agent role and vice versa. A line froman operator to an MIS denotes a connection.

Figure 7-3 MIS-MIS Connection Over Three Networks

In Figure 7-4, Figure 7-5, and Figure 7-6, objects which are shown in solid blackare non-local or remote objects.

In Figure 7-3, when operator O1 connect to MIS B1, the MIT will appear to theuser to contain objects from B1, net1, net2, net3. The MIT then appears as inFigure 7-4.

B1

net1 net2 net3

O1

O3

O2


7

Figure 7-4 Local and Non-local Objects as Seen from MIS B1

In Figure 7-3, when operator O2 connects to MIS net1, the MIT will appear tocontain objects from net1, net2, and net3. The MIT then appears as inFigure 7-5.

Figure 7-5 Local and Non-local Objects as Seen from MIS net1

sys=B1sys=net3sys=net2sys=net1

Root

sys=net3sys=net2sys=net1

Root


7

In Figure 7-3 when operator O3 connects to MIS net3, the MIT will only containobjects which are local to net3, as in Figure 7-6. In this scenario it would also bepossible to allow operator O3 to see objects from net2 and net1 by mountingnet2 and net1 on net3. This would give operator O3 the same access asoperator O2.

Figure 7-6 Objects Seen from MIS net3.

7.1.2 Event Forwarding Discriminators (EFDs)

An Event Forwarding Discriminator (EFD) is an ISO standards-basedmechanism for disseminating event information. EFDs are a managed objectclass defined in ISO DMI (ITU X.721 ISO/IEC 10165-2). They include adiscriminator construct attribute (frequently referred to simply as a“discriminator”), a destination attribute, and other (optional) attributes. Thediscriminator construct specifies a filter which the MIS uses to test eventinformation. Event information that passes the test is sent to each destinationspecified by the EFD destination attribute.

When an EFD is used to pass event information from one EM MIS to another,the MIS that sends the event is acting as the Agent. The MIS that receives theevent acts as the manager.

When you establish a connection, the MIS Manager defines and creates adefault Event Forwarding Discriminator (EFD) to be used for the specifiedMIS-to-MIS connection. However, the MIS Manager Advanced Settingswindow (see Section 7.2.2.2, “Advanced Settings Window”) enables you todefine and create a non-default EFD on the remote MIS machine. Refer to the

sys=net3

Root


7

subsection “Discriminator” in Section 7.2.2.2, “Advanced Settings Window”and Section 7.3.1.2, “Connecting to an MIS with a Non-default EFD” forinstructions. Refer also to Appendix D, “CMIS Scoping and Filtering” forinformation on constructing filters.

You can also log events forwarded from another MIS. To do this, you mustcreate a log object containing a discriminator which will create log records forthe desired events. Refer to Section 7.4, “Logging Events Sent from AnotherMIS” for instructions.

7.2 Using MIS ManagerThe following sections describe how to use the Solstice EM MIS Manager. Youcan use this application to establish a connection between your local MIS and aremote MIS.

7.2.1 Starting the MIS Manager

By default, you cannot start the MIS Manager from the Solstice EM ApplicationLauncher. You can, however, add the MIS Manager to the Launcher if youdesire, and then launch MIS Manager accordingly. For instructions on addingan application to the launcher, refer to the chapter entitled “ApplicationLauncher” in the Solstice EM Reference Manual.

To start the MIS Manager from the command line, use the following command:

The optional parameters are shown in Table 7-1.

host% em_mismgr [options] &


7

Table 7-1 Optional Parameters for the em_mismgr Command

7.2.2 Using MIS Manager Windows and Menus

The MIS Manager interface consists of two windows:

• Basic Settings Window — This is the window which appears when you firstinvoke the MIS Manager, or when you select Basic Settings from eitherwindow. You can use this window if your MIS-to-MIS connection will usethe default EFD and port.

• Advanced Settings Window — This window appears when you selectAdvanced Settings. Use this window if you are not using the default EFDand/or port.

7.2.2.1 Basic Settings Window

When you first invoke MIS Manager, the MIS Manager Basic Settings windowappears as illustrated in Figure 7-7:

Option Description

-help Print list of options (with descriptions) for theem_mismgr command.

-host < hostname> Specify the <hostname> of a remote MIS.

-port < port> Specify the port number (default is 5555).

-break Break the connection.

-remote <remote_MIS> Specify the remote MIS.

-discrim <discriminator> Specify the discriminator construct. Default is“and:{} ”.


7

Figure 7-7 MIS Manager Main Window

The Basic Settings window contains the following elements:

FileClick on File in the Basic Settings window menu bar to invoke the File menu.The File menu consists of the following option:

ExitSelect File➤Exit to close the MIS Manager application.

HelpClick on Help in any window to see a window displaying context-specific helpinformation.


7

Basic SettingsIf the Basic Settings window is the current window, the Basic Settings buttonappears as selected. This is the default setting when you first invoke MISManager, and therefore this window appears as the main window. From theAdvanced Settings window, you can click on the Basic Settings button to returnto the Basic Settings window. Use the Basic Settings window if you are notexplicitly defining the EFD and Port to use for the MIS-to-MIS connection.

Advanced SettingsClick on Advanced Settings to see the Advanced Settings window. Thiswindow enables you to explicitly define which EFD and/or port to use for thatMIS-to-MIS connection.

MIS:In this field, enter the hostname on which the remote MIS resides. This entrycannot be the local host (the machine on which MIS Manager is currentlyrunning).

ConnectClick on the Connect button to establish a connection between the local MISand the specified remote MIS.

DisconnectClick on the Disconnect button to terminate the specified MIS-to-MISconnection.

7.2.2.2 Advanced Settings Window

The Advanced Settings window is identical to the Basic Settings window,except that it offers two additional fields: Discriminator and Port. Use thiswindow if you want to explicitly define and create the EFD and port to be usedfor the MIS-to-MIS connection.

Click on the Advanced Settings button in the Basic Settings window to see theAdvanced Settings window as illustrated in Figure 7-8:


7

Figure 7-8 MIS Manager Advanced Settings Window

The Advanced Settings window contains the following elements:

FileClick on File in the Advanced Settings window menu bar to invoke the Filemenu. The File menu contains the Exit option.

ExitSelect File➤Exit to close the MIS Manager application.

Basic SettingsClick on the Basic Settings button to return to the Basic Settings window. Thisis the default setting when you first invoke MIS Manager, and therefore theBasic Settings window appears as the main window. Use this window if youdo not want to explicitly define an EFD and Port for the MIS-to-MISconnection.


7

Advanced SettingsIf the Advanced Settings window is the current window, the AdvancedSettings button appears as selected. This window enables you to explicitlydefine which EFD and/or port to use for that MIS-to-MIS connection.

MIS:In this field, enter the hostname on which the remote MIS resides. This entrycannot be the local host (the machine on which MIS Manager is currentlyrunning).

Discriminator:In this field, enter the definition for the Event Forwarding Discriminator to becreated and used for the MIS-to-MIS connection. For information onconstructing an EFD definition (CMIS filter), refer to Appendix D, “CMISScoping and Filtering” in this manual.

Port:In this field, enter the Port Number of the port to be used for the MIS-to-MISconnection. The default Port Number is 5555.

ConnectClick on the Connect button to establish a connection between the local MISand the specified remote MIS.

DisconnectClick on the Disconnect button to terminate the specified MIS-to-MISconnection.


7

7.3 Configuring MIS-to-MIS CommunicationThis section describes the specific steps involved in setting up MIS-to-MISCommunication.

7.3.1 Connecting to a Remote MIS

MIS Manager provides two options for connecting to an MIS:

• Use the Basic Settings window to connect to an MIS using the default EFDdefined and created by the MIS Manager.

• Use the Advanced Settings window to connect to an MIS using a non-default EFD you have explicitly defined.

7.3.1.1 Connecting to an MIS with a Default EFD

Do the following to connect to a remote MIS, using the default EFD:

1. On the managing MIS machine, bring up MIS Manager.

2. In the MIS field, enter the name of the remote MIS.

3. Click on the Connect button in the MIS Manager main window.

The MIS Manager will define and create the default EFD (and:{} ) andestablish a connection with the specified MIS.

7.3.1.2 Connecting to an MIS with a Non-default EFD

To connect to a remote MIS using a non-default EFD, do the following:

1. Bring up MIS Manager.

2. Click on the Advanced Settings button.

3. In the MIS field, enter the name of the remote MIS.Enter the name of the machine on which the remote MIS is running.

4. In the Discriminator field, enter the definition (CMIS filter) of the remoteEFD.


7

The default EFD consists of the following CMIS filter definition:

For information on CMIS filtering, refer to Appendix D, “CMIS Scoping andFiltering” in this manual.

5. In the Port field, enter the (remote) port number to be used for theconnection.The default port number is 5555. If you want to use a non-default portnumber, enter that number in this field.

6. Click on the Connect button to establish a connection between the localand remote MISs.

7.4 Logging Events Sent from Another MISIn order to log events forwarded from one MIS to another MIS, you mustcreate a log object containing a discriminator which will create log records forthe desired events. Do the following:

1. Bring up the Log Manager application.

2. Create a log object.Select Object➤New... from the Log Manager main window and enter theappropriate information in the window fields. (Refer to Chapter 13, “LogManager” in this manual for more detailed instructions on creating a logobject.)

To log every event that the Manager MIS receives, enter the followingdiscriminator definition in the discriminatorConstruct field:

To log all attributeValueChange events in one log record, enter thefollowing in the discriminatorConstruct field:

and:{}

and : {}

item : equality : {eventType, attributeValueChange}


7

This log object will log each attribute value change known by the local andforwarding MIS.

3. Set administrativeState to Unlocked.In the Create Log window, select Unlocked for the administrativeStateoption.

4. Select OK to create the new log object.


7

Part 2 — Applications

8-1

Application Launcher 8

8.1 OverviewThe Solstice EM Application Launcher is used to start the applicationsprovided with Solstice EM. Initially, the Application Launcher provides accessonly to the core (primary) applications provided with EM. However, you canalso add other Solstice EM or third-party EM applications to the Launcher.

8.2 Starting the Application LauncherYou must invoke the Application Launcher from the command line. To do so,enter the following command at the operating system prompt:

Overview page 8-1

Starting the Application Launcher page 8-1

Using the Application Launcher Windows, Icons, and Menus page 8-2

Adding, Modifying, and Deleting Icons page 8-10

hostname% em [-help] [-host < hostname>] &


8

The optional parameters for the em command are as follows:

Note – If the Application Launcher fails to connect to the MIS, the applicationicons in the main window are greyed out.

You can also start the Application Launcher and connect to a remote MIS bysetting the $EM_SERVER environment variable to the name of the remote hostwhere the MIS is running. Then at the command line, enter the em commandwith no options.

If you have enabled Access Control, and are not root , a UserId windowappears. Enter your user name and password. Depending upon the user accessrights assigned to you by the system administrator, you may have restrictedaccess to some, or all, of the Solstice Enterprise Manager applications orfeatures. Restricted applications and features are grayed out.

Note – Environment variables cannot be set from the Launcher. If your thirdparty application requires certain environment variable settings, you can setthese from a script and then start the Launcher from that script.

8.3 Using the Application Launcher Windows,Icons, and Menus

When you invoke the Application Launcher, the main window appears asillustrated in Figure 8-1:

Option Description

-help Print list of options (with descriptions) for the emcommand.


Application Launcher 8-3

8

Figure 8-1 Application Launcher Main Window

The main window displays graphical representations (icons) for the launchableapplications. Select an icon to launch that application. By default, the followingprimary applications can be launched from the Application Launcher mainwindow:

• Viewer — This is the main EM tool for monitoring and controlling networkand system resources.

• Discover — Provides a simple and convenient way to add managed objectsto the Management Information Server (MIS) database.

• Request Designer — Enables you to create query requests for monitoringmanaged objects on your network.

• Object Editor (OBED) — Displays a window through which you can viewand modify any of the objects in an EM MIS Management Information Tree(MIT).


8

• Alarm Manager — Enables you to create and monitor event alarms for EMmanaged resources.

• Log Manager — Enables you to create log objects.

• Log Viewer — Enables you to browse the contents of a log record.

• SNMP Browser — Enables you to view, modify, and set the contents of anSNMP MIB.

• Access Manager — Enables you to control user and group access toapplications.

• Data Collector — Enables you to create Data Collection Entry objects.

8.3.1 File Menu

Select File from the Application Launcher main window to see a pulldownmenu containing the following options:

• Reconnect

• Application Properties...

• Exit

These options are described in the following sections.

8.3.1.1 Reconnect

Select File➤Reconnect to reconnect to the MIS. If the Launcher is alreadyconnected to an MIS, this option is greyed out. When reconnecting, if theLauncher previously connected successfully (under access control), then noUserId window (login/password query) appears.

8.3.1.2 Application Properties...

Select File➤Application Properties... to see the Configure Applications windowas illustrated in Figure 8-2:


8

Figure 8-2 Configure Applications Window

This window enables you to add or change launching information forLauncher applications.

The Configure Applications window contains the following elements:


8

ApplicationsThis is a selection list of the applications currently accessible from theApplication Launcher. Select an item from this list to view information aboutthat application.

Application InformationThis area of the Configure Applications window contains several fields andcommand buttons. These are as follows:

Number of ColumnsSpecifies the number of columns in which to display the application icons.

Path to ExecutableEnter the complete pathname for the application executable, including anyarguments to the command.

Path to IconEnter the complete pathname for the icon to display for this application.

Icon NameEnter the string you wish to be used as the icon label. For multi-line labels,use the characters \n to indicate a line break.

EM Application (YES) (NO)Specify whether the application is an EM application by clicking on theappropriate button.

EM Application NameEnter the EM Application Name. This is the name used by the application toconnect to the MIS. It must be the same as the name you specified whensetting up access control for the application with the em_accesscmd . If thisname is not correct and the application is under access control, the icon forthe application will be grayed out when the Launcher is started by a non-super user. If the Launcher is started by a super user or the user root , thenthis field is disregarded. In that case, the icon will not be grayed out, and theapplication can be started from the Launcher.


8

AddClick on Add to add the application to the Application Launcher.

ChangeClick on Change to set your changes to the configuration information for anapplication.

DeleteClick on Delete to remove the selected application from the ApplicationLauncher.

Save...Click on Save in the Configure Application window to see the Select Filewindow as illustrated in Figure 8-3:


8

Figure 8-3 Select File Window

The Select File window contains the following elements:

FilterEnter the absolute pathname you want to use as a filter. Click on the Filtercommand button (see below) to display the list of files located in the filterdirectory.

DirectoriesThis is a scrollable selection list of the directories under the current filter.Double click on an item to select it and move to that directory.


8

FilesThis is a scrollable selection list of the files under the current directory. Clickon an item to select it.

SelectionThis field displays the filename currently selected. You can also explicitlyenter the complete pathname and filename for a file and then click on OK toselect it.

OKClick on OK to save your Configure Applications modifications to thespecified file and dismiss the Select File window.

FilterClick on the Filter command button (see below) to display the list of fileslocated in the specified filter directory.

CancelClick on Cancel to dismiss the Select File window without saving the file.

Load...Select Load... from the Configure Applications window to see the Select Filewindow as illustrated in Figure 8-3, above. Select the desired file as describedabove, and click OK to load the file. Click on cancel to dismiss the Select Filewindow without loading a file.

8.3.1.3 Exit

Select File➤Exit from the main window menu bar to quit the ApplicationLauncher. Exiting the Launcher has no effect on applications previously startedfrom the Launcher; they continue to run.


8

8.4 Adding, Modifying, and Deleting IconsThis section provides step-by-step instructions on how to add, modify, ordelete icons in the Application Launcher main window. The main window (seeFigure 8-1) displays an icon for each application accessible from the Launcher.You can use the Configure Applications window to add, modify, or delete iconsand applications from the Launcher (see Figure 8-2).

Note – The Application Launcher does not check the validity of your entries inthe Configure Applications window. Errors are detected when you attempt tostart an application.

8.4.1 Adding an Application to theApplication Launcher

To add an application and its icon to the Launcher, do the following:

1. Create the application icon using an icon editor.

2. Select File➤Application Properties... from the Application Launcher mainwindow menu bar.The Configure Applications window appears (see Figure 8-2).

3. Set the Number of Columns value to the number of icons you wantdisplayed per line in the Application Launcher.

4. In the Path to Executable field, enter the pathname for the executable.

5. In the Path to Icon field, enter the pathname for the icon graphic file.

6. In the Icon Name field, enter the string to be used as the icon label.

7. Specify (Yes/No) whether the application is an EM Application.

8. In the EM Application Name field, enter the name the application uses toconnect to the MIS.

Note – If you are adding a non-EM application to the Launcher, you must firstuse the command em_accesscmd -add to create the Application Name. Referto Chapter 9, “Access Manager” and Chapter 23, “Command Line Options” formore details.


8

9. Click Add to have the application icon added to the ApplicationLauncher.The icon you added then appears in the Application Launcher mainwindow.

10. Click Save... to save the configuration information to a file for later use.The Select File window appears. Specify the name of the file where thisconfiguration information is to be saved. The default file is theem_panel.cf configuration file.

8.4.2 Modifying the Launching Configurationfor an Application

To modify the Launching information for an application, do the following:


2. Select the application name in the Applications display area.The Application Information fields then displays the information pertainingto the selected application.

3. Enter your modifications.

4. Click Change to set your modifications.

5. Click Save... to save the modified configuration information to a file forlater use.The Select File window appears. Specify the name of the file to which thisconfiguration information is to be saved. The default file is~/em_panel.cf .


8

8.4.3 Deleting an Application from theApplication Launcher

To remove an application from the Launcher, do the following:


2. Select the icon item in the Applications display area.The fields in the Application Information area of the configuration windowshould now reflect the information for your selection.

3. Click Delete in the Configure Applications window.

4. Click Save... to save the configuration information to a file for later use.The Select File window appears. Specify the name of the file to which thisconfiguration information is to be saved. The default file is~/em_panel.cf .

9-1

Access Manager 9

9.1 OverviewThe Access Manager allows users to control access to Solstice EM applications.EM provides two types of access control:

• Application Access is the ability of the platform to grant or deny a user theability to run an application that has been registered with the MIS.

• Application Feature Access enables an EM application to restrict access tospecific features within that application on a per user basis. UnlikeApplication Access, Feature level access is enforced by the application, andthe MIS is used only to store the list of features for each application.

The Access Manager allows the user to create users and groups that define auser’s access for Application and Application Feature Access.

Overview page 9-1

Enabling and Disabling Access Control page 9-3

Granting Super User and Trusted Host Access page 9-4

Starting the Access Manager page 9-6

Using Access Manager Windows and Menus page 9-8


9

The Access Manager is intended for use by network administrators who areresponsible for controlling access to the network management tools. TheAccess Manager can also be used by end users who want to view their level ofaccess.

The Access Manager is constrained by the access control provided by the MIS.While the Access Manager allows administrators to create users and groups,each individual tool must conform to the access control mechanismsimplemented by the MIS in order to provide feature level control.

Note – To use Access Manager to control access for a third party EMapplication, you first must use the command em_accesscmd to define theapplication and its features. (Refer to the chapter entitled “Command LineSummary” in this manual for instructions.) Then you can use Access Managerto control access for that application.

Note – You can run only one instance of Access Manager or one instance ofem_accesscmd at a time. You cannot run these two programs simultaneously.

9.1.1 User Levels

The Access Manager provides two levels of access control. The level of accessprovided is determined by which type of user is running the tool:

• The user root has access to all Access Manager functions. You must beroot to create or modify user profile objects or application profile objects.The root-level user is typically referred to as “admin user.”

• Users other than root can view user privileges but cannot modifyprivileges. If a non-privileged user runs the Access Manager, all buttonsrelated to features that create, delete, or modify user and group privilegesare grayed out. Non-privileged users are typically referred to in this manualas an “end users.”

9.1.2 Groups

The concept of groups is an abstraction that simplifies administering useraccess. When a user profile is created for a user, the object has an attribute thatincludes groups to which the user belongs. This information is used by the

Access Manager 9-3

9

Access Manager to make the task of configuring users easier. Any admin whowants different access levels or policies can create a different group for eachaccess level or policy.

9.2 Enabling and Disabling Access ControlWhen you install Solstice EM, you are queried as to whether you want toenable access control. The following holds true, depending on your answer tothe query:

• When you answer Yes, the access control variables in the configuration fileEM-config are set to TRUE. You are then prompted as to whether you wantto invoke the Access Manager application.

• If you answer No to the access control query, then these variables are set toFALSE. You are not queried as to whether you want to start the AccessManager.

“Yes” is the default.

When you start Access Manager with access control disabled, a messagewindow telling you that access control is disabled. To use the Access Manager,you must the re-enable access control.

To enable/disable access control (after installation), do the following:

1. Log in as root.

2. Edit the assignments for the access control variables in the configurationfile $EM_HOME/build/acct/EM-config .

Note – Alternatively, you can modify the access control variables in theconfiguration file /var/opt/SUNWconn/em/conf/EM-config . When yourun em_services -r , your changes will not persist, and the access controlsettings revert to the assignments in $EM_HOME/build/acct/EM-config .


9

The table below describes the these variables and what their contents shouldbe for enabling and disabling access control.

Refer to the Chapter “Developing EM Solutions” in the Solstice EnterpriseManager Application Development Guide for details concerning thisconfiguration file.

3. Restart the MIS.After you have modified these variable assignments, you must restart theMIS with the following command:

After enabling access control, you may also want to define certain users assuper users, and specific remote hosts as trusted hosts. The following sectionprovides instructions for doing so.

9.3 Granting Super User and Trusted Host AccessWhen access control is enabled, super users are granted full access privilegesto controlled applications, and are not subject to password authentication. Togrant super user privileges to a user, you must add the user name to theassignment list for the variable EM_ACCESS_SUPER_USERS in theconfiguration file EM-config .

When super users connect from a remote machine, for full access to be granted,that remote host name must be defined as a trusted host. To define a host astrusted, add the host name to the assignment list for the variableEM_ACCESS_TRUSTED_HOSTS in the EM-config file.

Table 9-1 Access Control Variables in EM-config File

Variable Name Description Enable Disable

EM_ACCESS_PASSWORD_CONTROL Toggles password authentication. TRUE FALSE

EM_ACCESS_CONNECTION CONTROL Toggles access control. TRUE FALSE

EM_ACCESS_BACKWARD_COMPATIBILITY If this is TRUE, you can connect toEM2.0 MIS with applications linkedwith EM1.2 libraries when run as asuper user from a trusted host.

TRUE FALSE

host% em_services -r <hostname> &

Access Manager 9-5

9

The procedure is as follows:

1. Login as root.

2. Edit the super user and trusted host variable assignments in theconfiguration file $EM_HOME/build/acct/EM-config .

Note – Alternatively, you can modify the super user and trusted host variablesin the configuration file /var/opt/SUNWconn/em/conf/EM-config . In thiscase, when you run em_services -r , your changes do not persist, and thesettings revert to the assignments in $EM_HOME/build/acct/EM-config .

Note – The user root is by definition a super user by default, and thereforeneed not include it in the EM_ACCESS_SUPER_USERS variable assignment.

Table 9-2 describes the super user and trusted host variables and theircontents.

Table 9-2 Super User and Trusted Host Variables in EM-config

Variable Name Description

EM_ACCESS_SUPER_USERS This is a space separated list of super userUserIds. These users have full access controlprivileges. Password authentication is stillrequired if the user is connecting from a remotemachine. On the local machine, (or from a trustedhost), no password authentication is required. Youneed not include root in this list.

EM_ACCESS_TRUSTED_HOSTS This is a space separated list of host names. If theuser root or super users (defined in the variableEM_ACCESS_SUPER_USERS) are connectingfrom a trusted host, then no passwordauthentication is required and full access controlprivileges are granted. The local host is implicitlyconsidered a trusted host. By adding a host nameto this variable assignment, you can run daemonsremotely without being subject to access controlor password authentication.


9

3. Restart the MIS.After you have modified these variable assignments, you must restart theMIS with the following command:

Note – Note: Any changes to $EM_HOME/build/acct/EM-config do nottake effect until the next em_services -r .

9.4 Starting the Access ManagerYou can start the Access Manager in either of two ways:

• From the Application Launcher

• From the operating system command line

Each of these methods is described below.

9.4.1 Starting the Access Manager from theApplication Launcher

You can start the Access Manager by selecting the Access Manager icon in theApplication Launcher tool bar. To start up the Application Launcher, enter thefollowing command at the operating system prompt:

Where:-host <hostname> specifies the name of the machine on which the MIS isrunning.

For detailed instructions on using the Application Launcher, refer to theChapter 8, “Application Launcher,” in this manual.

host% em_services -r <hostname> &

host% em -host <hostname> &

Access Manager 9-7

9

9.4.2 Starting the Access Manager From theCommand Line

You can also invoke the Access Manager by entering this command at theoperating system prompt. As root , enter the following command:

The optional parameters are as follows:

# em_accessmgr [ -help ] [ -host < hostname>] &

Option Description

-help Print list of options (with descriptions) for theem_accessmgr command.



9

9.5 Using Access Manager Windows and MenusWhen you first invoke the Access Manager, the main window appears, asillustrated in Figure 9-1:

Figure 9-1 Access Manager Main Window

The Access Manager main window contains the following components:

Menu BarThe menu bar contains option buttons that invoke pull-down menus for AccessManager operations. The menu bar option buttons are:

• File

• Object

• View

• Help

Access Manager 9-9

9

Note – Click on Help in any window to see a window containing context-sensitive help information.

These menus and their options are described in detail in further sections of thischapter.

UsersClick on the Users selection button to see the list of existing users and thegroups to which they belong.

GroupsClick on the Groups selection button to see the list of existing groups andgroup members. Access Manager supplies the following default groups:

• View Only

• Operator

• Full Access

Users/Groups Display AreaThis area displays the current selection list for Users and Groups.

9.5.1 The File Menu

Select File from the main window menu bar to see the File pull-down menu.This menu contains the following options:

• Export...

• Import...

• Print...

• Exit

These options are described in the next sections.


9

9.5.1.1 Export...

Select File➤Export... to see the Export Customized window, as illustrated inFigure 9-2:

Figure 9-2 Export Customized Window

The Export Customized window contains the elements described below.

All Access Control ObjectsSelect All Access Control Objects to export all user and group access controlinformation for the current MIS to the specified file.

Users OnlySelect Users Only to export only User information for the current MIS to thespecified file.

Groups/Application Privileges OnlySelect this option to export all group and application access information for thecurrent MIS to the specified file.

Access Manager 9-11

9

File Name:In this field, enter the name of the file to which to export the specified accesscontrol information.

...Click on the “...” button beside the File Name field to invoke the Export to Filewindow, as illustrated in Figure 9-3:

Figure 9-3 Export to File Window

Use this window to select the file to which the access control informationshould be saved. The Export to File window contains the elements describedbelow.


9

FilterEnter the absolute path name of the filter, followed by an asterisk (*). Clickon the Filter command button (see below) to display the list of files locatedin the filter directory.

DirectoryThis scrollable selection list displays the directories under the current filter.Double click on an item to select it and move to that directory.

FilesThis scrollable selection list displays the files under the current directory.Click on an item to select it.

SelectionThis field displays the file currently selected. You can also explicitly enterthe complete path name and file name for a file, then click on OK to select it.

OKClick on OK to implement your selection and dismiss the Export to Filewindow.

FilterClick on the Filter command button to display the list of files located in thespecified filter directory.

CancelClick on Cancel to dismiss the Export to File without implementing yourselection.

OkClick on OK in the Export Customized window to save the access controlinformation to the specified file.

CancelClick on Cancel to dismiss the Export Customized window without exportingthe information to any file.

Access Manager 9-13

9

9.5.1.2 Import...

Select File➤Import... to invoke the Import from File window, as illustrated inFigure 9-4:

Figure 9-4 Import from File Window

This window enables you to read in an ASCII file containing access controlinformation for users, groups, and/or privileges. This file must have beencreated using the Export function described above. The imported accessinformation is created in the current MIS. This information is appended to anypre-existing information. No information is removed.

The Import from File window contains the elements described below.


9

FilterEnter the absolute path name you want to use as a filter. Click on the Filtercommand button (see below) to display the list of files located in the filterdirectory.


FilesThis scrollable selection list displays the files under the current directory.Double click on an item to select it.

SelectionThis field displays the file currently selected. You can also explicitly enter thecomplete path name and file name for a file, then click on OK to select it.

OKClick on OK to implement your selection and dismiss the Import from Filewindow.

FilterClick on the Filter command button to display the list of files located in thefilter directory.

CancelClick on Cancel to dismiss the Import from File without implementing yourselection.

Access Manager 9-15

9

9.5.1.3 Print...

Select File➤Print to see the Print options window, as illustrated in Figure 9-5:

Figure 9-5 Print Window

This window contains the elements described below.

Print to File:Click the selection box beside this field to send postscript output to a file. Enterthe preferred output file name in the Print to File: field.

...After selecting Print to File, click on the “...” button to see the File Selectionwindow as illustrated in Figure 9-6:


9

Figure 9-6 File Selection Window

This window contains the elements described below.

FilterEnter the absolute path name you want to use as a filter. Click on the Filtercommand button to display the list of files located in the filter directory.


Access Manager 9-17

9

FilesThis scrollable selection list displays the files under the current directory.Click on an item to select it.


OKClick on OK to implement your selection and dismiss the File Selectionwindow.


CancelClick on Cancel to dismiss the File Selection window without implementingyour selection.

Printer:In the Print window, click on the selection button next to the Printer field toprint output to the specified printer. Enter the name of the preferred printer inthe Printer field. You can also click on the down arrow button to see a pull-down list of available printers. Select the preferred printer name to enter it inthe Printer field.

CopiesEnter the number of copies you want. Click on the up/down arrows toincrease/decrease the specified number of copies.

Banner Page Title:Enter the string to be used as the banner page title.


9

TextClick on Text to print the current table information in text format.

TableClick on Table to capture a snapshot of the current table and print thesnapshot.

PrintClick on the Print button to print your selection.

CancelClick on the Cancel button to dismiss the Print window without issuing a printrequest.

9.5.1.4 Exit...

Select File➤Exit to quit the Access Manager.

9.5.2 The Object Menu

Select Object from the main window menu bar to see the Object pull-downmenu. This menu contains the following options:

• Create Group...

• Group Properties...

• Duplicate Group...

• Create User...

• User Properties...

• Duplicate User...

• Delete

• Select All

• Deselect All

These selections are described in the following sections.

Access Manager 9-19

9

9.5.2.1 Create Group...

Select Object➤Create Group... to see the Create Group window, as illustratedin Figure 9-7:

Figure 9-7 Create Group Window

The Create Group window enables you to create new access groups withspecific privileges.

Using the Create Group WindowThe Create Group window is divided into two sections. The left section is theCategories section, and the right section is the Forms Display section. Bothsections contain folder icons for the following:

• Group Description

• Group Members

• Group Privileges


9

If you click on these folders in either section, the information form for thatcategory appears in the Forms Display (right) section. If you open the GroupPrivileges folder in the either section, a folder for each of the controlledapplications appears in both sections. If you open an application folder icon ineither section, the access options for that application then appear in the FormsDisplay section. The application access options can be one or all of thefollowing:

• No Access

• Full Access

• Feature Access

If you select Feature Access, a selection button for each feature in thatapplication appears in the Forms Display section.

Figure 9-8 illustrates the Create Group window with the various folders open:

Access Manager 9-21

9

Figure 9-8 Create Group Window with Open Folders

The Create Group window contains the elements described below.


9

Name:Enter the new group name in the Name field.

Group DescriptionOpen the Group Description folder to show the Group Description field in theForms Display section. Enter the group description in this field.

Group MembersOpen the Group Members folder to display this form in the Forms Displaysection. The Group Members form contains the elements described below.

• All EM Managed Users: — This field displays a selection list of all EMmanaged users on the current host. Click on an item to select it.

• Members of Group: — This field displays a selection list of all members ofthe selected group. Click on an item to select it.

• Add >> — Click on Add>> to add a selected user from the All EM ManagedUsers selection list to the Members of Group list.

• Remove << — Click on Remove<< to remove a selected user from theMembers of Group list.

• Select All — Click on Select All below the preferred list to select all items inthat list.

• Deselect All — Click on Deselect All below the preferred list to deselect allitems in that list.

Group PrivilegesOpen the Group Privileges folder to display this form in the Forms Displaysection. The Group Privileges form contains the elements described below.

• Access Privileges: — Select one of the following options:• All Applications — Select All Applications to grant access permission to

the group for all controlled applications. The access options for anyapplications folders that are open are greyed out, and Full Access appearsas selected.

• Application Specific — Select Application Specific to explicitly definewhich controlled applications are accessible to the group. This makes theaccess options contained in the application folders available.

Access Manager 9-23

9

• Applications Folders — Each application controlled by Access Manager hasa folder icon. Open a folder to display the access options for thatapplication. These can be one of the following:• No Access — Select No Access to deny the group access to this

application.• Full Access — Select Full Access to grant the group access to this

application and all controlled features for this application.• Feature Access — Select Feature Access to grant access to only the selected

features for this application. If this option is available for an application,the selection list of available features appears in the application form.Click on the selection button to toggle access for a given feature.

Command ButtonsThe Create Group window contains the command buttons, located at thebottom of the screen, described below.

OKClick on the OK button to submit the Create Group data and dismiss thewindow.

ApplyClick on the Apply button to submit the Create Group window data withoutdismissing the window.

CancelClick on the Cancel button to dismiss the window without creating a newgroup.

9.5.2.2 Group Properties...

Select Object➤Group Properties... to see the Group Properties window asillustrated in Figure 9-9:


9

Figure 9-9 Group Properties Window

Notice that the Group Properties window is identical to the Create Groupwindow. The Group Properties window enables you to modify the accessspecifications for an existing group. To edit the properties for a group, do thefollowing:

1. Select the group you want to modify.You can select a group and bring up the Group Properties information forthat group by either of these methods:

• Click on the group entry in the main window table and then selectObject➤Group Properties.

• Double click on the group in the main window table.

The information for that group is loaded into the Group Properties windowforms.

2. Open the folder for the information you want to modify.Click on a folder icon in either section of the window to open the form forthat category.

Access Manager 9-25

9

3. Enter your changes.

4. Apply your changes.Click on the Apply button to apply your changes without dismissing thewindow, or on OK to apply the changes and dismiss the window.

Refer to Section 9.5.2.1, “Create Group...,” above, for a detailed description ofthis window.

9.5.2.3 Duplicate Group

Select Object➤Duplicate Group... to see the Duplicate Group window, asillustrated in Figure 9-10:

Figure 9-10 Duplicate Group Window

Notice that the Duplicate Group window is identical to the Create Group andGroup Properties windows. The Duplicate Group window enables you to copythe access specifications for an existing group to another group. To duplicate agroup, do the following:


9

1. Select the group you want to duplicate.Before invoking the Duplicate Groups window, select the group you want toduplicate.

2. Display the Duplicate Group window.Select Object➤Duplicate Group. A duplicate of the selected group is createdand the information is loaded into the access information forms. TheDuplicate Group window appears, with the duplicated group informationdisplayed.

3. Enter the name of the new group.Enter the name for the new group in the Name field and press Return. Thenew group is then created. Instead of pressing Return, you can also selectApply (to create the group without dismissing the window) or OK (to createthe group and dismiss the window).

Refer to Section 9.5.2.1, “Create Group...,” for a detailed description of thiswindow.

9.5.2.4 Create User...

Select Object➤Create User... to see the Create User window, as illustrated inFigure 9-11:

Access Manager 9-27

9

Figure 9-11 Create User Window

The Create User window enables you to define access for a new managed user.This window contains the elements described below.

User Login:Enter the login ID for the new user in this field. The login ID must be a validlogin ID for the host on which the current MIS is running.

Full Name:Enter the name of the new user in this field.


9

All EM Managed Groups:This area displays a selection list of all existing EM managed groups. Click onan item in this list to select it.

Membership of User:This area displays a selection list of all groups to which the new user belongs.Click on an item to select it.

Add >>Click on the Add>> button to add a selected group from the All EM ManagedGroups selection list to the Membership of User list.

Remove <<Click on the Remove<< button to remove a selected group from theMembership of User list.

Select AllClick on the Select All button located below a list to select all items in that list.

Deselect AllClick on the Deselect All button below a list to deselect all items in that list.

Command ButtonsThe Create User window contains the command buttons, located at the bottomof the screen, described below.

OKClick on the OK button to create the new user and dismiss the window.

ApplyClick on the Apply button to create the new user without dismissing thewindow.

Access Manager 9-29

9

CancelClick on the Cancel button to dismiss the window without adding a newuser.

9.5.2.5 User Properties...

Select Object➤User Properties... to see the User Properties window, asillustrated in Figure 9-12:

Figure 9-12 User Properties Window


9

Notice that the User Properties window is identical to the Create User window.The User Properties window enables you to modify the access specificationsfor an existing user. To edit the properties for a user, do the following:

1. Select the UserId and display the User Properties window.You can do this in either of two ways:

• Double click on the UserId in the User table in the main window. The UserProperties window automatically is displayed with the user information.

• Select the user from the User table in the main window, then selectObject➤User Properties.

2. Enter your changes.


Refer to Section 9.5.2.4, “Create User...” for a detailed description of thiswindow.

9.5.2.6 Duplicate User...

Select Object➤Duplicate User... to see the Duplicate User window, asillustrated in Figure 9-13:

Access Manager 9-31

9

Figure 9-13 Duplicate User Window

Notice that the Duplicate User window is identical to the Create User and UserProperties windows. The Duplicate User window enables you to duplicate theaccess specifications for an existing user to create a new user. Do the following:

1. Select the UserId and display the Duplicate User window.Select the user from the User table in the main window, then selectObject➤Duplicate User. The specifications for that user are duplicated, anddisplayed when the window is displayed.

2. Enter the UserId of the user you want to create.Enter the UserId of the new user in the User Login field of the new user tomodify it.


9

3. Enter the user’s name (optional).Enter the user’s name in the Full Name field of the window.

4. Modify the group membership(s) (optional).You can add to or remove membership from any group.


Refer to Section 9.5.2.4, “Create User...” for a detailed description of thiswindow.

9.5.2.7 Delete

Select a user or group in the display list, then select Object➤Delete to delete it.

9.5.2.8 Select All

Select Object➤Select All to select all users or groups in the display list.

9.5.2.9 Deselect All

Select Object➤Deselect All to deselect any current selections in the display list.

9.5.3 The View Menu

Select View from the main window menu bar to see the View pull-down menu.This menu contains the View Find... option. This option invokes the Findwindow, described in Section 9.5.3.2, “User Privileges.”

Access Manager 9-33

9

9.5.3.1 The Find Window

Select View➤Find to see the Find window, as illustrated in Figure 9-14:

Figure 9-14 The Find Window

The Find window enables you to find access control information for a user orgroup. This window contains the elements described below.

Find:This area of the screen presents two options, User and Group. Click on theappropriate selection button to specify the nature of your search.

Match On:This area of the screen presents two options, Exact String and Substring. Clickon the appropriate selection button to specify the type of string search.

Case SensitiveClick on this selection box to toggle the case sensitive search feature.


9

Search StringEnter the search string in this field.

FindClick on Find to initiate the search operation.

CancelClick on Cancel to dismiss the Find window without initiating a search.

9.5.3.2 User Privileges

Select View➤User Privileges... to see the User Privileges window, as illustratedin Figure 9-15:

Figure 9-15 User Privileges Window

Access Manager 9-35

9

The User Privileges window enables you to view a user’s access privileges foreach of the controlled applications. The window is divided into two sections.The left section displays the User Privileges folder; when this folder is open,the applications folders are accessible as well. The right section is the FormsDisplay section. When an application folder is open, this displays the user’saccess privileges for that application.

Note – This is a view-only window. You cannot modify the values in thiswindow. Therefore the option settings are grayed out.

The User Privileges window contains the elements described below.

User PrivilegesOpen the User Privileges folder icon to reveal the application folders. Theoptions described below also appear in the Forms Display section of thewindow.

Access Privileges:This displays the following options:

• All Applications — If shown as selected, the user has full access to allcontrolled applications.

• Application Specific — If shown as selected, the user has access privilegesas specified for each application and feature.

Applications FoldersEach application controlled by Access Manager has a folder icon. Open a folderto display the user’s access privileges for that application. These privileges canbe one of those described below.

No AccessIf shown as selected, the user does not have access privileges to theapplication.


9

Full AccessIf shown as selected, the user has full access privileges for this applicationand all controlled features for the application.

Feature AccessThis option displays Feature Access privileges for the user of theapplication. If this option is available for an application, the list of availablefeatures appears in the application form. If a user has access to a feature,that feature appears as selected.

10-1

Viewer 10

10.1 OverviewThe Viewer is the window into your network. It enables you to create, inspect,and monitor a View, which is a graphical representation of a set of relatedmanaged objects. You can create both topology-related and non-topology-related Views.

Either from the Viewer itself or through other EM tools accessed from theViewer, you can:

• View the managed objects in your network

• Switch among various Views of your network

• Monitor your network

• Find managed objects in the current View or in other Views

• Add managed objects

Overview page 10-1

Starting the Viewer page 10-5

Using the Viewer Windows and Menus page 10-7

Summary of Common Viewer Tasks page 10-59

The Viewer Configuration File page 10-67


10

• Launch requests against managed objects

• Receive data, reports, events, and traps from managed resources on yournetwork

• Selectively control which types of objects in a View to display

Warning – Because the Viewer has no security, all Views are public. However,access to the Viewer and its features can be controlled by the Access Manager.

10.1.1 Objects

The Viewer represents managed objects as icons. An icon can be one of thefollowing types:

• Container — This represents an object that can contain other objects. Forexample, the Internet universe in Figure 10-1 is a Container icon.

• Device — This represents an object that cannot contain any objects.Examples of elements are hosts, routers, and hubs.

• Link — This represents a link that connects other types of icons.

• Multimonitor (View) — This represents an object that can contain otherobjects, similar to a Container object. A multimonitor icon is separated intosections. Each section represents a View of an object contained in themultimonitor. The severity status of a given section represents the status ofthe object identified with the section. There are four types of multimonitoricons:• Hexagon — contains six object View sections• Hexagon120 — contains three object View sections• OmniSector — contains a single object View section• Circle — contains an arbitrary number of View sections. The maximum

number is 360.

A Viewer icon is actually a representation of a group of objects, including:

• a topology object (topoNode object), where the object is in a networktopology

• one or more Agent objects internal to the MIS that inform the MIS whichprotocol to use to access management data for that object.

Viewer 10-3

10

When you create or delete an object in the Viewer, you create or delete theobjects described above.

10.1.2 Views

A View is a graphical representation of a set of related managed objects. TheViewer Canvas—the area of the main window that displays icons representingobjects in your network— displays one View at a time. You can easily switch toother Views. You can also run multiple instances of the Viewer to displaymultiple Views simultaneously.

You can create both topology-related and non-topology-related Views. The twotypes of Views are illustrated in Figure 10-1, below.


10

Figure 10-1 Topology and Non-Topology Views

The two types of Views are described in the following sections.

10.1.2.1 Topology Related Views

As an example of a topology-related View, consider a network that containsmultiple subnetworks. The network might be one View and each subnetworkwithin it might constitute separate Views, with the network View containingthe subnetwork Views. In this way, topology-related Views mimic the topologyof a network. For example, in Figure 10-1, the topology-related Views are thebranches 129.146.0.0 and mpk16-076-n below the Root View.

View NavigatorCanvas

Topology-related Views

ViewerCanvasNon-topology-related

View

Viewer 10-5

10

10.1.2.2 Non-Topology Related Views

You also can have Views that are distinct from your network topology. Forexample, all of your administration building routers might be in one View andall of your campus file servers in another. Such logical groupings emanate fromthe Root View, in a branch distinct from the Internet View. Such non-topological Views can have child Views, if you create logical Views withinparent logical Views.

10.2 Starting the ViewerYou can start the Viewer in either of two ways:

• from the Application Launcher

• from the operating system command line

Note – If you start the Viewer without first running Discover (see Chapter 11,“Discover”), the Viewer displays only a Root View in the View Navigator (left)Canvas and no icons in the Viewer Canvas (window on the right). For moreinstructions, refer to Section 10.4.1, “Populating the Viewer” further on in thischapter.


10.2.1 Starting the Viewer from the ApplicationLauncher

You can start the Viewer by selecting the Viewer icon in the ApplicationLauncher toolbar. To start up the Application Launcher, enter the followingcommand at the operating system prompt:



10

Where the optional parameters are as follows:

For detailed instructions on using the Application Launcher, refer to Chapter 8,“Application Launcher.”

10.2.2 Starting the Viewer From the Command Line

You can also invoke the Viewer and have it connect to a remote MIS byentering this command at the operating system prompt:

The optional parameters are as described in the following table.

Option Description

-help Prints list of options (with descriptions) for the emcommand.

-host < hostname> Specifies the name of the machine on which the MIS isrunning.

hostname% em_viewer [options] &

Option Description

-help Print list of options (with descriptions) for theem_viewer command.

-host < hostname> Specify a remote machine where the MIS is running.

-no_move Object movement not allowed.

-r Do not initialize requests.

-view < view> Initial View.

-no_labels Do not display the object labels.

-no_scale Do not resize the object labels on zoom.

-ifont < fontname> Use the specified <fontname> for object labels.

Viewer 10-7

10

10.3 Using the Viewer Windows and MenusAfter you have invoked the Viewer, the main window appears, as illustrated inFigure 10-2:

Figure 10-2 Viewer Main Window

The Viewer main window contains the following components:

Title BarThe title bar displays “Solstice EM 2.0: Viewer” followed, in square brackets,by the name of the MIS machine to which this instance of the Viewer isconnected.

ViewNavigatorCanvas

MainWindowCanvas

Iconmenu

Gotobutton

Toolbar

Sash

CurrentViewName

Status Bar


10

Menu BarThe menu bar contains buttons which invoke pulldown menus for Vieweroptions and tools. The menu bar buttons are:

• File

• Object

• Edit

• View

• Tools

• Help


These menus and their options are described in detail in further sections of thischapter.

ToolbarThe main window toolbar contains icon buttons which invoke various Viewertools. The main window toolbar is explained in detail in Section 10.3.1, “Usingthe Main Window Toolbar,” below.

View Name FieldThis is a field displaying the current View name. By typing an object name inthis field, you can direct the Viewer to select and display that object. If theobject exists in more than one View, the Multiple Views window appears, asillustrated in Figure 10-3:

Viewer 10-9

10

Figure 10-3 Multiple Views Window

This window contains the following elements:

Views Containing: <object-name>This area displays a list of Views containing the specified object. Click on alist item to select it. You can also double-click on an icon to go to that View.

GotoClick on Goto to see the selected View and highlight the object.

CloseClick on Close to dismiss the Multiple Views window.


10

Goto ButtonClick the Goto button in the main window to see a pulldown menu displayinga list of the last seven Views you have visited during this session. To switch toa specific View, select it from the list. To go back to the parent View of theCurrent View, select “..” located at the top of the Goto menu.

Viewer CanvasThe Viewer Canvas is the large display area occupying the right portion of theViewer main window. This displays icons for the various managed objectswithin the current View.

View Navigator CanvasThe View Navigator Canvas occupies the left portion of the main window. Thisdisplays the overall topology (Views only) as one of the following:

• a tree with node named Root at the top when viewing only the local MIS

• a forest of trees, each with a root node named Root[<system-name> ]where <system-name> is the name of the MIS for that topology tree. Insingle MIS configurations, there will be only a single root name.

The topology is actually a directed graph rather than a tree because a topologynode can have more than one parent. For a View that has n parents, the Viewwill be duplicated in the View Navigator n times. The Viewer knows that all ncopies are the one and the same View, so you can click on any copy to displaythe View in the Viewer Canvas.

Border and SashBetween the View Navigator Canvas and the Viewer Canvas is a moveableborder. The border enables you to change the relative proportions of the twoviewing areas within the larger Viewer main window. Drag the sash, the smallbox near the base of the dividing border, to move the border back and forth.

Status LineThe status line is located at the bottom of the Viewer window, beneath theViewer Canvas. The right side of the status line displays the number of objectsin the View and the number of objects selected. In response to certain activities,the left side of the status line displays the status of an action that is in progress.

Viewer 10-11

10

After a short time, the status line will revert back to displaying the highestseverity. The percentage figure in the middle of the status line signifies thecurrent Zoom percentage.

10.3.1 Using the Main Window Toolbar

The Viewer main window contains a toolbar of icons for invoking variousViewer and EM tools. The main window toolbar is illustrated in Figure 10-4:

Figure 10-4 Viewer Main Window Toolbar

Select an icon in the toolbar to invoke the corresponding tool. For OCT, youcan first select a managed object in a View and then select a tool icon; thisapplies the functions of that tool to the selected object. The following tools areprovided in the Viewer main window toolbar for all Views:

OCT IconSelecting this icon invokes the Object Configuration Tool. The ObjectConfiguration Tool is discussed in Chapter 19, “Object Configuration Tool.”

View Properties IconSelecting this icon invokes the View Properties window. You can also invokethis window by selecting View➤View Properties... from the main windowmenu bar. Refer to Section 10.3.7.1, “View Properties...” for instructions onusing this window.

OCT ViewProperties

Layers ZoomIn

ZoomOut

ZoomReset

ZoomArea

ZoomZoomHistoryForward

HistoryBack


10

Layers IconSelecting this icon invokes the View Layers window. You can also invoke thiswindow by selecting View➤Layers from the main window menu bar. Refer toSection 10.3.7.3, “Layers...” for instructions on using this window.

Zoom IconsThe Zoom icons are as follows:

• Zoom In — Each time you click on this icon, the current View is magnifiedby the percentage that you have set as the Zoom Factor in your ViewProperties sheet.

• Zoom Out — Each time you click on this option, the current Viewmagnification is reduced by the percentage you have set as the Zoom Factorin your View Properties sheet.

• Zoom Area — If you hold down the SELECT (left) mouse button, you canselect a rectangular zoom area in the current View by moving the mouse.After you have selected this target area for enlargement, it will become theentire View if you select Zoom Area.

• Zoom Reset — If you select this option, the zoom level is reset to 100%.

• Zoom History Back — Click on the Zoom History Back icon to go backwardin the zoom history. This icon is grayed out when you are at the beginningof the zoom history.

• Zoom History Forward — Click on this icon to go forward in the zoomhistory. This icon is grayed out when you are at the end of the zoom historywhich is normally the case until you hit the Zoom History Back.

Map View Area ControlsIf your current View uses a geographical map background, you will also seesome additional tool icons to the right of the Zoom icons:

Viewer 10-13

10

• Map Centering — If you select this icon, the map centering cursor appears.Click on the point on the map that you want to become the center of theView. That point then becomes the center reference point for the currentView.

• Map Pan — If you select this icon, the cursor turns into a hand with a fingerpressed against the map. Move the mouse while holding down the Selectbutton to pull the map in the direction of the mouse movement.

10.3.2 Using Object Icons

The icons representing the various managed objects are displayed in theViewer Canvas area.

Many Viewer operations effect the currently selected objects. You can selectobjects for operations as follows:

• You can select a region of objects by holding down the Select button andmoving the mouse. A selection area rectangle appears as you move themouse. Release the mouse button to select all objects in that region.

• Click the Transfer (middle) button on an icon to select or deselect that objectfrom a group of selected objects.

• You can double click on an icon to invoke a Default Activation (user-configurable operation) on that icon. By default, the following activationsoccur:• For Container and Monitor objects, the selected object becomes the current

View.• For all other topology types, the Object Configuration Tool (OCT) is

invoked for modifying that object.

Map pan

MapCentering

Pan controls


10

10.3.3 Using the Object Icon Menus

Click the right mouse button on any Object icon in the Viewer Canvas to see apulldown menu for that icon. The icon menus enable you to performoperations on the managed objects represented by the icons. You can alsoconfigure customized icon menus for each object type (refer to Section 10.5.1.2,“Icon Menus Section” for instructions).

By default, the Icon menus contain one or all of the following options:

Object Properties…Select Object Properties... from an icon menu to invoke the ObjectConfiguration Tool. Detailed instructions for using OCT are provided inChapter 19, “Object Configuration Tool.”

SNMP Browser...Select SNMP Browser from an icon menu to invoke the SNMP Browserapplication. Detailed instructions for using this application are provided inthe chapter entitled “SNMP Browser,” in this manual.

Data Viewer…Select Data Viewer... from an icon menu to invoke the Data Viewerapplication. Detailed instruction for using this application are provided inthe chapter entitled “Data Viewer,” in this manual.

Alarm Manager…Select Alarm Manager... from an icon menu to invoke the Alarm Managerapplication. Detailed instructions for using this application are provided inthe chapter entitled “Alarm Manager,” in this manual.

Go To ViewSelect Go To View from an icon menu to switch to the View contained by theContainer icon.

Clear Alarms...Select Clear Alarms... from an icon menu to clear all outstanding (open) alarmsposted against the topology node represented by that icon.

Viewer 10-15

10

10.3.4 File Menu

Select File... from the main window menu bar to see a pulldown menucontaining the Exit option.

ExitSelect Exit to terminate the Viewer application.

10.3.5 Object Menu

Select Object from the menu bar to see a pulldown menu containing optionsfor adding and configuring new objects for the current View. These options areas follows:

New ContainerSelect Object➤New Container to see a pullright menu of Container subtypes.When you select a New Container type, the Object Configuration Tool windowappears as illustrated in Figure 10-5:


10

Figure 10-5 Object Configuration Window.

After you configure the object in OCT and click on the OK button, the objectwill appear in the current View. The initial position of the object is usually tothe right of the last icon on the bottom row. Refer to Chapter 19, “ObjectConfiguration Tool” for instructions on using this utility.

Viewer 10-17

10

New DeviceSelect Object➤New Device to see a pullright menu for creating and addingnew Device objects to the current View.

New LinkSelect Object➤New Link... to create a link between objects. The Viewer willprompt you to select the two object icons to be connected. Once you haveselected the two objects, the Object Configuration Tool is invoked.

New MonitorSelect Object➤New Monitor... to create and add a new Multimonitor object tothe current View.

Object Properties...Select Object➤Object Properties... to invoke the Object Configuration Tool foroperations on all selected objects. Refer to the chapter entitled “ObjectConfiguration Tool” in this manual for instructions.

10.3.6 Edit Menu

Select Edit from the main window menu bar to see a pulldown menu withoptions for performing various edit operations. Using these options, you canedit icons in the current View, as well as create new Containers and Devices.The Edit menu options are as follows:

CopySelect Edit➤Copy to make a copy of the selected element(s). You can thenpaste this copy in another View by switching to that View and using theEdit➤Paste option.

PasteSelect Edit➤Paste to insert a copy from the last Edit➤Copy operation into thecurrent View. To copy elements into a View, you can select one or moreelements, copy them as described above, then go to the target View and pastethem into that View.


10

Note – To create a duplicate instance of an object in a different View, use theCopy and Paste options. However, if an object instance already exists in aView, you cannot paste another copy of it in that View. Multiple instances of anobject in a single View are not permitted.

DeleteSelect Edit➤Delete to remove the selected object(s) from the current View. Youalso can choose to delete the selected object(s) from all Views. This is usefulwhen objects have been copied to several different Views and you want toremove all instances.

Note – When deleting the last instance of an object, the Viewer also deletes anylinks that were attached to the object, all associated SNMP, RPC, or CMIPAgents, and any running requests targeted on the object.

Select AllSelect Edit➤Select to select all of the displayed objects belonging to the currentView. You can then copy, paste, or delete them all in one operation.

Deselect AllSelect Edit➤Deselect All to deselect all of the selected objects within thecurrent View.

Viewer 10-19

10

10.3.7 View Menu

Select View from the main window menu bar to see a pulldown menucontaining options for controlling how objects are displayed in the currentView. These options are:

• View Properties...

• Background Properties...

• Layers...

• Layout...

• Map

• Zoom

These menu options are described in the following sections.

10.3.7.1 View Properties...

Select View➤View Properties... to see the View Properties window, asillustrated in Figure 10-6:


10

Figure 10-6 View Properties Window

Viewer 10-21

10

Note – The Viewer stores the View properties in the configuration file$HOME/.em_viewer.cf . If this file cannot be found, the Viewer looks for$EM_HOME/config/em_viewer.cf .

The View Properties window contains a number of fields and controls forsetting properties for the current View. These are segregated into the followingwindow sections, according to purpose:

• Display — This contains fields and controls for setting View type, icon type,and Navigator Canvas orientation.

• Icon Size — This contains fields and controls for handling icon resizingduring Zoom operations.

• Icon Label Size — This contains options for determining how label resizingis handled during Zoom operations.

• Zoom — This contains the control for setting the Zoom incrementpercentage.

• View Colors — This contains options and controls for setting object displaycolor. The Modify... button leads to the Color Chooser window.

• Icon Status Color Source — This contains options for specifying the datasource for icon color changes.

• Command buttons — The command buttons at the bottom of the ViewProperties window enable you to apply, set, or cancel your changes, andaccess online help.

Each section and its contents are described in detail below.


10

View Properties Default SettingsThe following are the default values for the View Properties parameters:

Table 10-1 View Properties Default Settings

Category Parameter Default Value

Display

Display: Logical View

Navigator Orientation: Vertical

Default View: Root

Icon Size

Scale Icon Size ON

Fixed Icon Size OFF

Small OFF

Medium ON (When Fixed IconSize is ON)

Large OFF

User Defined OFF

Zoom

Increment of Jump 20%

View Colors

Navigator: White

Canvas: White

Object Labels: Black

Object Selection Color Red

Icon Status ColorSource

Alarm Severity OFF

Propagated Alarm Severity ON

User Defined <greyed out>

Viewer 10-23

10

These parameters are described in detail in the following sections.

Display ParametersThe Display section of the View Properties window contains the followingfields:

Display:The Display: field provides two options, Logical View and Geographical View.Logical View is the default. Geographical View enables you to associateelements with a position on a geographic map, such as buildings on a campusmap or cities on a regional map.

Note – In order to use Geographical Map mode, you must add a geographicalmap to the current View. See Section 10.3.7.2, “Background Properties….” forinstructions.

Navigator Orientation:Select Horizontal or Vertical to specify the layout you desire for theNavigator Canvas. Icon trees will be orientated accordingly.

Icon Size ParametersThe Icon Size section of the View Properties window provides controls fordetermining icon resize handling during Zoom operations. The options are asfollows:

Scale Icon SizeClick on the Scale Icon Size button to turn this feature on. When ON, Zoomoperations will resize icons according to the increment specified in theVariable Icon Size Setting window (see “Modify...,” below).

Modify...When Scale Icon Size is ON, the Modify... button is functional. Click onModify... to see the Variable Icon Size Setting window as illustrated inFigure 10-7:


10

Figure 10-7 Variable Icon Size Setting

The Variable Icon Size window contains the following elements:• Minimum <value> Percent of Normal Size/at <value> Percent Zoom —

Click on the up and down arrows in the Minimum Percent of Normal Sizefield to increase/decrease this value. Click on the up and down arrows inthe adjacent At <value> Percent Zoom field to set the Zoom percent.

• Maximum <value> Percent of Normal Size/at <value> Percent Zoom —Click on the up and down arrows in the Maximum Percent of Normal Sizefield to increase/decrease this value. Click on the up and down arrows inthe adjacent At <value> Percent Zoom field to set the Zoom percent.

• OK — Click on OK to set your values and dismiss the window.• Cancel — Click on Cancel to clear and dismiss the window.

Fixed Icon SizeClick on the Fixed Icon Size button to turn off the Scale Icon Size feature anduse the specified Fixed Icon Size. When Fixed Icon Size is selected, icons willnot resize during zoom operations. The remaining Icon Size options are thenavailable for specifying the fixed icon size.

• Small (50%) — When Fixed Icon Size is selected, select Small to set thefixed icon size to 50% of the actual size.

• Medium (100%) — When Fixed Icon Size is selected, select Medium to setthe fixed icon size to the default size.

• Large (150%) — When Fixed Icon Size is set to ON, select Large to set thefixed icon size to 150% of the actual size.

Viewer 10-25

10

• User Defined — Select User Defined to set the fixed icon size to a specificpercentage. Click on the up/down arrow buttons in the Percent % field toincrease/decrease the percentage, respectively.

Note – You can click on the Apply button at the bottom of the View Propertieswindow to see the effects of your selection before permanently setting iconresize handling.

Icon Label Size ParametersThe Icon Label Size section of the View Properties window provides twooptions for resizing icon labels during Zoom operations:

Scale Label with IconResize labels so that the label height is approximately 20% of the iconheight.

Fixed Label SizeMaintain fixed label size (regardless of icon size) during Zoom operations.

Zoom ParametersThis section of the View Properties window contains the following parameterfield:

Increment of Jump:Use this field to specify the resize percentage for Zoom operations. Click onthe up/down arrow buttons to increase/decrease the Zoom incrementpercentage, respectively. To see the effects of your selection, click on theApply button (described below). Then use the Zoom In and Zoom Out iconson the main window toolbar to see the results. You can also use the Zoomoptions in the View pulldown menu (see below).


10

View Colors ParametersThe View Colors section of the View Properties window contains controls forsetting background colors for the following items:

• Navigator Canvas

• Viewer Canvas

• Object Labels

• Object Selection

The current color setting for an item is displayed in a small color sample box tothe left of the item. To change a color, select the item and click on the Modify...button to display the Color Chooser window (described below).

Modify...Click on Modify... in the View Colors section to see the Color Chooserwindow as illustrated in Figure 10-8:

Viewer 10-27

10

Figure 10-8 Color Chooser Window

The Color Chooser window provides controls for editing the selected itemcolor. These controls are divided into three sections:• Color Sample• Color Editor• Command Buttons

These are described in the following subsections.


10

Color SampleThis section of the Color Chooser window contains the following items:

Old The is a small sample box (left box) displaying the current color for theitem.

NewThis is a small sample box (right box) displaying the new color for theitem. As you adjust the color controls, the New Color Samplesimultaneously displays your changes.

Grab ColorThis enables you to select a color from an item anywhere on your screen.Click on the Grab Color button; the cursor will change to a cross. Movethe cursor to the desired color on your screen, and click the left mousebutton. The New Color Sample box displays the selected color.

Color EditorThe Color Editor section of the Color Chooser window contains thefollowing controls:

R, G & BMove the slider bars to modify the red, green, and blue values for thecolor.

HueMove the slider bar to modify the proportions of red, green, and blue forthe color.

SaturationMove the slider bar to modify the degree of saturation (purity) for thecolor.

ValueMove the slider bar to modify the dark/light value for the color.

Viewer 10-29

10

Command ButtonsThe command buttons are at the bottom of the Color Chooser window.These are:

OKSelect OK to set your color selections.

CancelSelect Cancel to abort the Modify Color operation and dismiss the ColorChooser window.

Icon Status Color SourceThis section of the View Properties window contains parameters for controllingwhich data source to use to determine the color of the icons. The options are asfollows:

Alarm SeverityClick on the Alarm Severity button to use this as the color source. Thiscolors each icon based on the most severe outstanding alarm posted againstthe topology node. The default color mapping for alarm severity is asfollows:

• red — critical• orange — major• cyan — minor• yellow — warning• blue — indeterminate

Propagated Alarm SeverityClick on the Propagated Alarm Severity to turn on this feature. This colorseach icon based on the propagated severity of each topology node. Fortopology nodes without children, this is the same as Alarm Severity.However, for Containers, the propagated severity is the most severeoutstanding alarm posted against the Container and all the topology nodescontained within the Container. This is evaluated recursively for Containerswhich contain Containers, etc. This is the default setting.


10

User-DefinedThis is an advanced option which allows you to use your own data to drivethe icon color. The icon color is based on the values set in thetopoNodeDisplayStatus attribute of topology nodes. This attributecontains a list of tag/value pairs, e.g.:

Typically, you would write your own client/daemon program which wouldupdate the topoNodeDisplayStatus based on your criteria. Note that inorder for the tag values, e.g. Netload and MySeverity , to appear in theUser-Defined option menu, you must add the tags to the topoAllStatusattribute of the topoNodeDB=NULL object, for example:

The same color mapping used for severities is used for the user-definedvalues; consequently, the values must be between 0 and 5. You can add morecolor mappings, as well. This requires using the Object Editor tool to addmore objects. Refer to Chapter 20, “Object Editor/Browser” for instructionson adding objects.

Command Buttons (View Properties Window)The command buttons are located at the bottom of the View Propertieswindow. These are:

OKClick OK to set your changes and dismiss the View Properties window.

ApplyClick Apply to see your changes in the current View. The View Propertieswindow will remain. Click OK to set the changes and exit the ViewProperties window.

{ {"Netload", 4 } , {"MySeverity", 3}}

{"Netload", "MySeverity" }

Viewer 10-31

10

CancelClick on Cancel to dismiss the View Properties window withoutimplementing any changes.

10.3.7.2 Background Properties…

Select View➤Background Properties to see the Background Properties window,shown in Figure 10-9:

Figure 10-9 Background Properties Window

Use this window to select a background image or geographical map for thecurrent View. Sun Rasterfile is the supported bitmap background format. Thebackground image appears if you have selected Logical View mode in the ViewProperties window. The geographical map is displayed if you have selectedGeographical Map mode. Each object in the View has a logical location and ageographical location. The logical location is an abstract x,y coordinate whilethe geographical location is a longitude, latitude coordinate which locates theobject on a particular point in the world.

The Background Properties window contains the following components:

Container Name:This displays the name of the selected Container icon.


10

Bitmap (sunraster):Enter the name of the desired bitmap file in this field. Click on the “...” buttonto the right to see a Select File window for selecting a bitmap file. The SelectFile window is described in the next section.

Geographical Map:Enter the name of the desired geographical map file in this field. Click on the“...” button to the right to see a Select File window for selecting a geographicalmap file. The Select File window is described in Section , “Select File...,” onpage 10-33.

Several sample geographical maps are provided with your Solstice EMdistribution.

Note – To install them, answer 'Y' when asked “Do you want to install theGeographical Map Data?” by the em_install script. The sample map data, ifinstalled, is located in the directory $EM_HOME/mapdata.

OKClick on OK to set the selected file as the background and dismiss theBackground Properties window.

ApplyClick on Apply to apply the selected file as the background. The BackgroundProperties window remains.

CancelSelect Cancel to clear and dismiss the Background Properties window.

Note – In order for the bitmap background image to appear in the View, youmust select Logical View in the Display field of the View Properties sheet.

Viewer 10-33

10

Select File...From the Background Properties window, click on the “...” button to the rightof either the Bitmap or Geographical Map fields to see the appropriate SelectFile window. You can use this window to select the file you want to use as yourbackground. An example of a Select File window is illustrated in Figure 10-10.


The Select File window contains the following components:

FilterThis field displays the current directory from which you can select a file. Youcan also enter a directory name to switch to a new directory.


10

DirectoryThis area displays a list of the subdirectories contained in the current directory.Use the scrollbar to scroll through the list. Select an item from this list to moveto that subdirectory.

FilesThis area displays a list of the files contained in the current directory. Select abackground file from this list. The absolute pathname and filename for the fileappears in the Selection field.

SelectionThis displays the absolute pathname and filename for the selected file. You canalso type in the absolute pathname for a file to select that file.

FilterThis field displays the current directory path. You can also type in an absolutepathname and press Return to move to that directory.

OKClick on OK to set your selected file as the background.

CancelClick on Cancel to cancel the Select File operation and dismiss the window.

Viewer 10-35

10

10.3.7.3 Layers...

Select View➤Layers... to see the Layers window, as illustrated in Figure 10-11.

Figure 10-11 Layers Window

All object types are assigned to different logical layers. You can use thiswindow to specify which object layers will be displayed in your Views. Bydefault, Views display all object layers. Your selection will apply to all Viewsthroughout the current instance of the Viewer.

The Layers window contains the following components:


10

Map Layers...Click on the Map Layers button in the Layers window to see the Map Layerswindow, as illustrated in Figure 10-12:

Figure 10-12 Map Layers Window

The Map Layers window allows you to select which layers of the geographicalmap to display for the current View. The Map Layers window contains thefollowing components:

Viewer 10-37

10

Display:Select one of the following:

• All Map Layers — Display all map layers in all Views of the currentinstance of the Viewer.

• Selected Map Layers — Display only the selected map layers in all Viewsof the current instance of the Viewer. Selecting this option displays a list ofavailable map layers in the Map Layers: section of the window.

Map Layers:When you choose Selected Map Layers, a selection list of available maplayers appears in this display area. Use the vertical and horizontal scrollbarsto move through the list. Click on an item to select it.

OKClick on the OK button to implement your selections for all Views in thecurrent instance of the Viewer.

ApplyClick on the Apply button to see the effects of your selections on all Viewsin the current instance of the Viewer.

CancelClick on the Cancel button to abort your changes and dismiss the window.

Display Background ImageClick on Display Background Image in the Layers window to display yourselected background image.

Display:Select one of the following in the Layers window:

• All Object Layers —Display all object layers in all Views of the currentinstance of the Viewer.

• Selected Object Layers — Display only the selected object layers in all Viewsof the current instance of the Viewer. Selecting this option displays a list ofavailable object layers in the Object Layers: section of the window.


10

OKClick on the OK button in the Layers window to implement your selections forall Views in the current instance of the Viewer.

ApplyClick on Apply in the Layers window to see the effects of your selections on allViews in the current instance of the Viewer.

CancelClick on Cancel in the Layers window to abort your changes and dismiss thewindow.

10.3.7.4 Layout...

Click on View➤Layout... to see the Layout window as illustrated inFigure 10-13:

Figure 10-13 Layout Window

The Layout window provides controls for setting the number columns fordisplaying objects in the current View. The Layout window contains thefollowing components:

Number of ColumnsMove the slider bar to specify the number of columns for displaying icons inthe current View. Drag the slider to the right to increase or to the left todecrease the number of columns value.

Viewer 10-39

10

LayoutClick on the Layout button to see the effect of your new settings in the currentView.

CloseClick on the Close button to abort your changes and dismiss the window.

Note – Your modifications will affect only the current View for that specificinstance of the Viewer. If you add new icons to the current View aftermodifying the settings, the new icons will not be aligned accordingly in thedisplay. You must click on the Layout View button again after adding newicons to apply the settings to those icons.

10.3.7.5 Map

Select View➤Map to see a pullright menu containing the following options:

Note – If the current View does not use a geographical map, this option will begrayed out.

CenterThis enables you to specify a point on the map as the center of the View.

Select Map➤Center; the cursor will change to a cross. Move the cursor to thedesired point on the map, and click the left mouse button once. That pointbecomes the center of the View. You can also click on a location in the smallreference window at the lower right to define a center point.

PanThis enables you to scroll to off-screen areas of the map. Select Map➤Pan. Thecursor will change. Move the mouse while holding down the left button to pullthe map in the direction of mouse movement.

Reset PropertiesSelect Map➤Reset Properties to set the current zoom level and map centerpoint as the respective defaults for the current View.


10

Default PropertiesSelect Map➤Default Properties to reset the default scale and center so that theentire map is visible.

10.3.7.6 Zoom

Select View➤Zoom to see the Zoom pullright menu. The Zoom menu containsthe following options:

InSelect View➤Zoom➤In to magnify the current View by the Zoom Factorpercentage specified in View Properties (see “Zoom In” in Section 10.3.1,“Using the Main Window Toolbar” for details).

OutSelect View➤Zoom➤Out to reduce the current View by the Zoom Factorpercentage specified in View Properties (see “Zoom Out” Section 10.3.1, “Usingthe Main Window Toolbar” for details).

AreaThis enables you to select a zoom area in the current View. Use the left mousebutton to select View➤Zoom➤Area and — continuing to hold down the leftmouse button — move the mouse to specify a rectangular zoom area in thecurrent View. Release the left mouse button to select the specified area forzooming. Now, reselect View➤Zoom➤Area to zoom in on the selected area inthe current View. You can also click on the Zoom Area icon to activate thezoom operation (see “Zoom Area” in Section 10.3.1, “Using the Main WindowToolbar” for details).

ResetSelect View➤Zoom➤Reset to reset the zoom level to 100% (see “Zoom Reset”in Section 10.3.1, “Using the Main Window Toolbar” for details).

Viewer 10-41

10

10.3.8 Tools Menu

Click on Tools in the main window menu bar to see a pulldown menucontaining a list of EM applications accessible from the Viewer. Select one ofthe items in the list to invoke that application.

The Tools options are either classified as fixed or user-configurable.

The fixed tools are as follows:

• Configure...

• Find...

• Requests...

• Object Palette...

• View List...

The user-configurable Tools options are as follows:

• SNMP Browser...

• Data Viewer....

• Alarm Manager...

• Log Manager...

• Log Viewer...

• MIS Manager

• Clear Alarms

These tools are described in the sections that follow.

10.3.8.1 Configure

Select Tools➤Configure to see a pullright menu containing options forconfiguring various components of the main window display. The options are:

• Tools Menu...

• Objects Menu...

• Default Activations...


10

Tools Menu…Select Tools➤Configure➤Tools Menu... to see the Configure Tools window asillustrated in Figure 10-14:

Figure 10-14 Configure Tools Window

Viewer 10-43

10

This window enables you to add additional applications to the Viewer mainwindow Tools menu. You can also specify arguments to be passed to theseapplications.

The Configure Tools window contains the following components:

Applications

This area of the window displays a list of the applications currently included inthe Tools menu. To view the Tools Configuration information for an item inthis list, click on the item. The information then appears in the ApplicationInformation fields in the Configure Tools window.

Application Information

This section of the window includes the following fields:

Application Name:Enter the name of the application (as you want it displayed in the Toolsmenu) in the Application Name: field. Any arguments required for theexecutable must be entered in the Arguments field (see below).

Path to Executable:Enter the absolute pathname for the executable in this field.

Arguments:Enter the keywords for any arguments required for the command. Thespecial variable macros (described in the tables below) are allowed. If any ofthe variable macros are present, the Viewer replaces the macro name with itscurrent value before executing the command.

The command macros are as follows:

Table 10-2 Command Macros

Variable Description

EM_GOTOVIEW For default activations and popup menus,changes the current View to the associated object.An error will result if the object is not a View(Container or Monitor type).

EM_VIEWERCONFIG Launches em_oct (Object Configuration Tool)


10

The variable macros are as follows:

Table 10-3 Variable Macros


EM_OBJNAME For default activations and popup menus,substitutes the name of the associated object. Fortools menu, substitutes the name of a selectedobject. If more than one icon is selected, the icon isused is arbitrary.

EM_OBJNAMES For default activations and popup menus,substitutes the name of the associated object. Fortools menu, substitutes the names of all selectedobjects.

EM_UNIQUE_ID Same as EM_OBJNAME, except the unique objectidentifier system-name:id is substituted insteadof the name. Use this to integrate with other EMapplications which accept the -id command-lineoption.

EM_UNIQUE_IDS Same as EM_OBJNAMES, except the uniqueobject identifier system-name:id is substitutedinstead of the name. Use this to integrate withother EM applications which accept the -idcommand-line option.

EM_VIEW Substitute the name of the current View.

EM_VIEW_UNIQUE_ID Same as EM_VIEW except the unique objectidentifier system-name:id is substituted insteadof the name. Use this to integrate with other EMapplications which accept the -id command-lineoption.

EM_MIS Substitute name of the MIS system to which theViewer is connected.

Viewer 10-45

10

The obsolete variables are as follows:

AddClick on Add to add the application to the Tools menu.

ChangeTo change the information for an application already included in the Toolsmenu, first select the item in the Applications list. Then click on Change tomodify the information for that application. To save your changes anddismiss the window, click on the OK command button (see below).

DeleteTo delete an application from the Tools menu, first select the item in theApplications: list. Then click on Delete to delete the item from theApplications: list. To apply your changes to the Tools menu, click on theApply button (to save) or the OK button (to save and dismiss the window).

Command ButtonsThe command buttons, found at the bottom of the Configure Tools window, areas follows:

OKClick on OK to save your changes and dismiss the Configure Tools window.

ApplyClick on Apply to save your changes. The Configure Tools window remainsonscreen.

Table 10-4 Obsolete Variables


EM_ID Same as EM_OBJNAME except the objectidentifier id (unique in single-MIS configurationsonly) is substituted instead of the name.

EM_IDS Same as EM_OBJNAMES except the objectidentifier id (unique in single-MIS configurationsonly) is substituted instead of the name.


10

CancelClick on Cancel to dismiss the Configure Applications window withoutimplementing any changes.

Objects Menu...Select Tools➤Configure➤Objects Menu... to see the Configure Device Optionswindow as illustrated in Figure 10-15:

Figure 10-15 Configure Device Options Window

Viewer 10-47

10

You can use this window to specify the options for a pulldown menu attachedto a View icon. You can also copy the contents of one icon menu to anothericon menu.

The Configure Device Options window contains the following components:

Select Device TypeThis area displays a scrollable list of supported Device types. Select the type ofDevice for which you want to configure an icon menu.

Menu Options for Device Type “<device_type>”This section of the window contains a number of fields and controls forconfiguring icon menus. These are as follows:

Copy From Device Type:Click on the Copy From Device Type: button to see a list of currentlydefined Device icon menus. Select the Device type (icon menuconfiguration) you want to copy to the new menu configuration.

Menu Options:This area displays a list of the current icon menu options for the selectedDevice type.

Menu Option:Enter the menu option you want to add to the menu.

Command:Enter the command line for the option. If the command contains any of thespecial commands listed above in Table 10-2, Table 10-3, or Table 10-4, thespecial command is executed and the rest of the command line is ignored.Otherwise, if any of the variable macros listed in Table 10-3 are present, theViewer will replace the macro variable name with its current value beforeexecuting the command.

AddClick on Add to add the option to the selected menu.


10

ChangeClick on Change to modify a selected menu item.

DeleteClick on Delete to remove the selected menu item.

Command ButtonsThe Configure Device Options window contains the following commandbuttons, located at the bottom of the screen:

ApplyClick on Apply to apply your modifications.

ResetClick on Reset to clear the Configure Device Options window withoutapplying your changes.

CloseClick on Close to close the Configure Device Options window.

Default Activations...Select Tools➤Configure➤Default Activations... to see the Default Activationswindow as illustrated in Figure 10-16:

Viewer 10-49

10

Figure 10-16 Default Activations Window

The Default Activations window enables you to specify the action that is tooccur when you double click on an item in the Viewer window. By default, thecommand for an element or Link icon is EM_VIEWERCONFIG, which is thecommand that brings up the Object Configuration Tool. For a Container icon,such as a network, the default command is EM_GOTOVIEW, which causes theViewer to switch to the View contained in that icon.



10

Device TypesThis area of the window displays a selection list of the available Device types.Click on an item to select it.

Device InformationThis area of the window contains the following elements:

TypeThis displays the selected Device type. You can also enter the Device type inthis field.

CommandEnter the command line for the option. If the command contains any of thespecial commands listed above in Table 10-2, Table 10-3, or Table 10-4, thespecial command is executed and the rest of the command line is ignored.Otherwise, if any of the variable macros listed in Table 10-3 are present, theViewer will replace the macro variable name with its current value beforeexecuting the command.

UpdateClick on Update to update the Default Activations information for that type.

Command ButtonsThe Default Activations window contains the following command buttons,located at the bottom of the screen:

ApplyClick on Apply to apply your modifications.

ResetClick on Reset to clear the Default Activations window without applyingyour changes.

CloseClick on Close to close the Default Activations window.

Viewer 10-51

10

10.3.8.2 Find

Select Tools➤Find... to see the Find window as illustrated in Figure 10-17:

Figure 10-17 Find Window

Find provides a means to search the MIS for the specified object or groups ofobjects according to object name and/or object type (the latter as specified inthe Object Palette).

When searches are successful, Find returns a list of matching object(s). Theseobjects are represented by a collection of icons in the Find window.


10

The Find window contains the following components:

MIS:The label for the adjacent button displays the name of the selected MIS. Clickon the button to see a selection list of available MISs. Select an MIS from thelist; your selection is displayed in the button label.

Object NameIn this field, specify the name of the object(s) for which you want to search.

Object TypeThe label for the adjacent button displays the name of the selected Object Type.Click on the button to see a selection list of available Object Types. Select anitem from the list; your selection is displayed in the button label.

Find ResultsThe Find Results area displays the icon(s) representing the object(s) found fromyour search criteria. Use the scroll bars to navigate through the Find Resultsdisplay.

GotoClick on an object and then click on the Goto button to see the View containingthat object.

Add to...Click on Add to... to see the Find: Add to window as illustrated inFigure 10-18:

Viewer 10-53

10

Figure 10-18 Find: Add to Window

This window enables you to save found objects to a specified (new or existing)View.

The Add to window contains the following components:

View Name:Enter the name of the View to which results should be added. If you enterthe name of an existing View, the found objects are added to that View. Ifany of the found objects already exist in the target View, duplicates of theseobjects are not created. New Views for found objects are created under theRoot View with the name you entered. An icon for that View is displayed inthe View Navigator Canvas and the name of that View appears in the ViewList.

SaveClick on Save to save the Find results to the specified View.

CancelClick on Cancel to cancel your save request and dismiss the window.

RemoveClick on Remove in the Find window to delete an object from the Find Resultsdisplay.


10

FindClick on Find in the Find window to search for objects according to yourspecified search criteria.

CloseSelect Close to dismiss the Find window.

10.3.8.3 Requests

Select Tools➤Requests to see the Requests window as illustrated inFigure 10-19:

Figure 10-19 Requests Window

The Requests window enables you to do the following:

Viewer 10-55

10

• Launch a new request based on one of the templates found in the RequestTemplates list.

• Invoke the Request Designer to examine, modify, or delete one of therequest templates found in the Request Templates list.

• Invoke the Request Designer to create a new request template and add it tothe Request Templates list.

The Requests window contains the following elements:

Available RequestsThis area of the window displays a list of the existing Request Templates.

StartClick on Start to start the selected request template on all the selected objects inthe current View. You can also start a request template by dragging the requesttemplate name from the Request Templates list (by holding down the middlemouse button), then dropping it over the icon of the object to which to send therequest.

Note – To launch a request at a selected target, the target object must have beenconfigured as supporting the appropriate Agent (SNMP MIB, SNM 2.x schema,or CMIP GDMO). You can use the Object Configuration Tool to change theobject’s Agent configuration. Requests are launched against the first Agentconfigured for the object in the OC tool list. For example, if you want to launcha PingUpOrDown request against an object, you must have deselected SNMPMIBs and selected the SNM 2.x ping schema.

Modify...To modify a particular request template, select it and then click on the Modify...button. This invokes the Request Designer. Refer to the “Request Designer”chapter in the Solstice Enterprise Manager Administration Guide for more detailedinformation on that application.


10

Create...To create a new request template, click on the Create button. This invokes theRequest Designer. Refer to the “Request Designer” chapter in the SolsticeEnterprise Manager Administration Guide for detailed information on thatapplication.

CloseClick on the Close button to dismiss the Requests window.

10.3.8.4 Object Palette

Select Tools➤Object Palette... to see the Object Palette window as illustrated inFigure 10-20:

Figure 10-20 Object Palette Window

Viewer 10-57

10

The Object Palette window contains icons and icon labels representing thetypes of objects you can add to a View. Selecting an icon from the ObjectPalette adds that object type to the current View and displays the ObjectConfiguration Tool (OCT) window. For information on the OCT window see,Chapter 19, “Object Configuration Tool.”

You can also drag and drop the icon from the Object Palette window into thecurrent View. If new object types (classes that can be represented as objects inViews) are added to the MIS, they automatically appear in the Object Palette.Refer to the chapter entitled “Adding an Object to the Object Palette” in theSolstice Enterprise Manager Administrator’s Guide for instructions.

10.3.8.5 View List...

Select Tools➤View List... to see the View List window as illustrated inFigure 10-21:

Figure 10-21 View List Window

The View Lists window enables you to select a new current View from theexisting (visited) Views.



10

View ListThis area of the window displays a list of the currently existing Views. Click onan item in this list to select it. Double click to go to that View.

Goto ViewClick on the Goto button to go to the selected View.

CloseClick on the Close button to dismiss the View List window.

10.3.8.6 SNMP Browser...

Select Tools➤SNMP Browser... to invoke the EM SNMP Browser application.The SNMP Browser enables you to view, get, and set data for SNMP MIBs.Refer to Chapter 16, “SNMP Browser,” for detailed information on thisapplication.

10.3.8.7 Data Viewer...

Select Tools➤Data Viewer to invoke the EM Data Viewer Application. TheData Viewer allows you to manipulate management data by performing a Geton a specified object or by setting attributes on an object. Refer to Chapter 17,“Data Viewer,” for detailed information on this application.

10.3.8.8 Alarm Manager…

Select Tools➤Alarm Manager... to invoke the EM Alarm Manager application.If an element is selected in the current View, the Alarm Manager displaysalarms only for the selected element. The Alarm Manager provides informationabout alarms received by the MIS. An alarm is an event or trap that has beenregistered (by a request) in the MIS. For information about the Alarm Manager,refer to Chapter 15, “Alarm Manager.”

10.3.8.9 Log Manager…

Select Tools➤Log Manager to invoke the EM Log Manager application. Forinformation about the Log Manager, refer to Chapter 13, “Log Manager.”

Viewer 10-59

10

10.3.8.10 Log Viewer…

Select Tools➤Log Viewer to invoke the EM Log Viewer application. If anelement is selected in the current View, the Log Viewer displays records onlyfor the selected element. For information about the Log View, refer toChapter 14, “Log Viewer.”

10.3.8.11 MIS Manager...

Select Tools➤MIS Manager to invoke the EM MIS Manager application. TheMIS Manager enables you to establish an MIS-MIS connection between localand remote MISs. Refer to Chapter 7, “MIS to MIS Communication” fordetailed information on this application.

10.3.8.12 Clear Alarms

To clear the alarms for a single topology node, select Clear Alarms from theobject icon popup menu.

To clear the alarms of multiple topology nodes, first select the icons, then selectTools➤Clear Alarms.

10.4 Summary of Common Viewer TasksThe following sections provide a quick reference guide to common Viewertasks.

10.4.1 Populating the Viewer

If you start the Viewer without first having run Discover (see Chapter 11,“Discover”), you have only a Root View in the View Navigator (left) Canvasand no icons in the Viewer Canvas (window on the right). The fastest way topopulate the Viewer is to run Discover, which creates a new branch orbranches under the Root View.

You can also create logical Views, which are, by definition, not related tonetwork topology.


10

10.4.2 Creating a Viewer Icon

You can use any of the following methods to create object icons in the Viewerwindow:

• Select Object➤<new-object-type>. Select the appropriate object type from theObject pulldown menu selections. For example, if you are creating aContainer icon, select “New Container” from the Object pulldown menu.Then select the icon type from the object pulldown menu. This invokes theObject Configuration Tool (OCT) application. For information about theOCT window see, Chapter 19, “Object Configuration Tool.”

• Select Tools➤Object Palette... to open the Object Palette window. Select anicon from the window. Refer to Section 10.3.8.4, “Object Palette” forinstructions.

• Select Tools➤Find… to invoke the Find window. Use Find to locate thedesired objects and click on Add To… in the Find window to create a newContainer View. Refer to Section 10.3.8.2, “Find” for instructions.

10.4.3 Configuring a Viewer Icon (Device,Link, Container, or Multimonitor)

After using the Object Palette to create an object instance or a View, use theObject Configuration Tool, as described in Chapter 19, “Object ConfigurationTool,” to name and assign other attributes to the new object. You can launchthe Object Configuration Tool by selecting Configure... in the pulldown menuattached to that icon. For Device icons, OCT can also be launched by double-clicking on the icon.

In the Object Configuration Tool, you can change the type of a Device, forexample, from a Router to a Server. However, you cannot change the type of aConnection, Container, or Multimonitor.

10.4.4 Performing a Get or Set Request

Select Data Viewer... in the pulldown menu attached to the (Link or Device)icon for the target-managed object. This invokes the EM Data Viewerapplication. Refer to Chapter 17, “Data Viewer” for instructions on using thisapplication.

Viewer 10-61

10

10.4.5 Checking on the Alarms for a Managed Object

Select Alarm Manager... in the pulldown menu attached to the (Device) icon forthe target-managed object. This brings up the Alarm Manager, described inChapter 15, “Alarm Manager.”

10.4.6 Clearing Alarms

To clear all outstanding alarms against one or more topology nodes, you cando one of the following:

• To clear the alarms of a single topology node, select Clear Alarms from theobject icon menu.

• To clear the alarms of multiple topology nodes, first select the icons, thenselect Tools➤Clear Alarms.

Note – Invoking Clear Alarms on a Container will not clear the alarms of theobjects within the Container.

10.4.7 Propagating Alarm Severity to Parent Views

You might want the display of Alarm Severity for an object icon to propagateto its parent Container (for example, to see when a machine was down withina subnetwork). To use this feature, first select View➤View Properties. In theView Properties window, then click on the Propagated Alarm Severity buttonto invoke this function.

10.4.8 Displaying and Selecting an ObjectLocated in the Current View

To display and select an object located in the current View, type the name ofthe object in the Current View Name field (located to the right of the Gotobutton in the main Viewer window shown in Figure 10-2), then press Return.This is particularly effective if the current View is large and some of its objectsare not visible within the Viewer Canvas.


10

10.4.9 Switching Views

You can use any of the following methods to switch between Views:

• Activate a View icon in the View Navigator Canvas. (If necessary, move thesash to enlarge the View Navigator Canvas.)

• Click on the Goto button in the main window to see the list of recentlyvisited Views. Select the desired View from this list to go to that View.

• Enter a View name in the View Name field (located to the right of the Gotobutton) and press Return. If there are multiple Views with that name, thenthis invokes the Multiple Views window, as described in Section , “ViewName Field,” on page 10-8.

• Select Tools➤View List to see the View LIst window. Select the desired Viewfrom this window. See Section 10.3.8.5, “View List...” for instructions.

10.4.10 Searching Multiple Views for an Object

To search for objects in multiple Views, enter the object name in the CurrentView Name field (located to the right of the Goto button in the main Viewerwindow), then press Return. The Multiple Views window appears, asillustrated in Figure 10-3. This window lists all the Views that contain theobject. To open one of the other Views, select it from the list and click on Goto.

10.4.11 Changing the View Navigator Orientation

To change the View Navigator Canvas orientation from vertical to horizontal,invoke View➤View Properties. In the View Properties window, set ViewNavigator Orientation to horizontal. The change takes effect immediately.

10.4.12 Zooming In or Out

You can increase the magnification of the View by the following methods:

• Zoom in on a selected area.

• Make the selected area fill the entire View Canvas.

• Increase the magnification of the current View by a selected percentage.

The Zoom controls are accessible by two means:

Viewer 10-63

10

• Select View➤Zoom to see the Zoom pulldown menu; select the desiredaction from this list.

• Use the zoom icons in the Viewer main window toolbar.

10.4.13 Toggling the Display of an Object Typein a View

Each of the standard object types is on a distinct logical layer. By default, all ofthese layers are displayed for each View. If a large number of object types arepresent in a single View, you might want to turn off the display for selectedtypes. You can control which of these layers are displayed in a given View byusing the Layers window. Select View➤Layers to invoke this window. Refer toSection 10.3.7.3, “Layers...” for instructions.

10.4.14 Adding an Object to the Viewer’sObject Palette

This section provides instructions for adding a new object type to the ObjectPalette. In this example, you will create a new Container class object calledSatellite .

1. Decide the class of object you want to add.First, determine what the object class is for the object you want to add(Device, Link, Container) to the Object Palette. In this example a newSatellite object that behaves like the existing Host object is being added.

2. Next, edit the file /var/opt/SUNWconn/em/conf/init_user to providethe pertinent information.For example, to add Satellite as a new Device class, init_user wouldhave the entry shown below (note that you must use the exact punctuationas shown):


10

By default, Solstice EM provides this example in the init_user file butthe lines are commented out.

3. Create an icon for the Satellite Device class object.Create an icon and save it to the following file:

/opt/SUNWconn/em/glyphs/Satellite.pm .

The Viewer application will look for the Satellite.pm file to obtain theicon associated with the Satellite Device class. This icon must be in Xpixmap format (xpm). Other formats may be incompatible with the Viewer.

4. Use one of the following methods to instantiate the Satellite object in theMIS.• If you want to make the new object type available in the Object Palette

without restarting the MIS, enter the following command at a systemprompt:

• If you use the em_services utility, the MIS is restarted and the -i optionerases all existing information in the MIS, although the init_user file ispreserved.

CREATE{OC = topoTypeSOI = ’topoTypeDBId=NULL’topoTypeId = SatellitetopoTypeDerivedFrom = ’{ “Device” }’topoTypeDrawMethod=squaretopoTypeDefaultLayer = Default}

#em_objop -f init_user

#em_services -i

Viewer 10-65

10

10.4.15 Adding New Geographical Maps forthe Viewer

Geographical map files are ASCII configuration files that list the componentgeographical layer files and format files (if any) to be used to construct themap background. By default, the geographical map configuration filenameshave the extension.gmc .

Note – You must select Geographical View in the Display field of the ViewProperties window to use the geographical map feature.

Several sample geographical maps are included with Solstice EM. If you wantadditional geographical maps, these can be obtained from Strategic Mapping,Inc.

To add a new map to the Viewer, you first need to create a Geographical MapConfiguration (GMC) file to indicate the labels for the map layers. You can thenuse the Map Layers window to specify which map layers to display.

The following section describes the contents of the Geographical MapConfiguration file. Section 10.3.7.3, “Layers...” describes how to use the Layersand Map Layers windows to control display of map layers.

10.4.15.1 Geographical Map Configuration File

The Geographical Map Configuration file consists of three sections. The firstsection specifies the absolute path to the location of the actual map data files:

Where:

TvFileDir <absolute-pathname> specifies the absolute pathname of thedirectory containing the files.

Note – You need not store the map data files in the same location as the GMCfile, since the GMC file contains the absolute path to the data.

TvFileDir <absolute-pathname>


10

The second section of the GMC file contains optional lists of files used to storegraphical format or symbol information such as colors:

Where:

TvStyleSheet <relative-pathname> specifies the relative pathname to thegraphical format file.

TvSymbols <relative-pathname> specifies the relative pathname to the filecontaining the symbol information.

The third section of the GMC file contains the list of all component data filesthat are used to construct the map. This section consists of a table with threecolumns. An entry in this table has the following format:

The column at the left must contain either a “Y” or “N” for each entry. Thisindicates whether the specified map layer is to be displayed by default. Thesecond column is the file name of the actual map data. The column on the rightis text string (within double quotes) to be used as the label for the map layer inthe Map Layers window. The following is a sample GMC file:

TvStyleSheet <relative-pathname>TvSymbols <relative-pathname>

Y | N <relative-pathname> “ <label>”

Viewer 10-67

10

10.5 The Viewer Configuration FileWhen the Viewer application is started, it looks for the configuration file$HOME/.em_viewer.cf . This file contains the variable assignments for yourViewer preferences. If this file is not in the customary location, the Viewersearches in the directory /opt/SUNWconn/em/config/em_viewer .

You can edit this file to customize various aspects of the Viewer interface, suchas Viewer menus, menu options, and command invocations.

The following sections describe the contents of the Viewer configuration file.

TvFileDir /opt/SUNWconn/em/mapdata/so-caTvStyleSheet TvStyleSheetTvSymbols TvSymbolsY Apodj.tv “DCW: Areas - Political & Ocean”Y Appdj.tv “DCW: Areas - Populated Places”Y Ldndj.tv “DCW: Areas - Rivers & Lakes”Y Lpodj.tv “DCW: Lines - Ocean Features”Y Lrddj.tv “DCW: Lines - Roads”Y Lrrdj.tv “DCW: Lines _ Railroads”Y Ltsdj.tv “DCW: Lines - Bridges & Tunnels”Y Lutdj.tv “DCW: Lines - Pipelines & Power Lines”Y Pdndj.tv “DCW: Lines - Rivers & Lakes”Y Pdsdj.tv “DCW: Lines - Misc. Rivers & Lakes”Y Pofdj.tv “DCW: Point - Ocean Features”Y Ppodj.tv “DCW: Point - Political & Ocean”Y Pppdj.tv “DCW: Point - Populated Places”Y Tdndj.tv “DCW: Text - Rivers & Lakes”Y Tpodj.tv “DCW: Text - Political & Ocean”Y Tppdj.tv “DCW: Text - Populated Places”Y Trddj.tv “DCW: Text - Roads”Y Tutdj.tv “DCW: Text - Pipelines & Power Lines”


10

10.5.1 File Format

The Viewer configuration file comprises the following sections:

• View Properties

• Icon Menus

• Default Activations

• Layers

• Tools Menu

The contents of these sections are described below.

10.5.1.1 View Properties Configuration Section

The first section of the Viewer configuration file contains variable assignmentscorresponding to the View Properties window parameters. The View Propertiesparameters are described below in Table 10-5:

Table 10-5 Viewer Configuration File — View PropertiesParameters

Variable Assignable Value Description

DefaultView <viewname> The View which appears bydefault when you start theViewer.

NavigatorOrientation {Vertical | Horizontal} Orientation of NavigatorCanvas display.

IconColorSource {AlarmSeverity |PropagatedAlarmSeverity |User-defined}

Specifies the icon colorsource.

ViewStyle {Logical | Geographic} Specifies the default Viewdisplay type.

ZoomFactor <non-negative-integer> Specifies the increment ofjump.

GlyphSizeFixed {True | False} Specifies whether Fixed IconSize is On (True) or Off(False).

Viewer 10-69

10

LabelSizeFixed {True | False} Specifies whether Fixed LabelSize is On (True) or Off(False).

MinIconSizePercent <non-negative-integer> Minimum percent for iconzoom size.

MinIconZoomLevel <non-negative-integer> Minimum icon zoom level.

MaxIconSizePercent <non-negative-integer> Maximum percent for iconzoom size.

MaxIconZoomLevel <non-negative-integer> Maximum icon zoom level.

FixedGlyphSizePercent <non-negative-integer> Percent size for fixed iconsize.

ObjectLabelFg rgb#<n>/<n>/<n>Where: <n> is 0-255.

Color used for Object IconLabel foreground.

ViewerCanvasBg rgb#<n>/<n>/<n>Where: <n> is 0-255.

Color used for Viewer Canvasbackground.

NavCanvasBg rgb#<n>/<n>/<n>Where: <n> is 0-255.

Color used for NavigatorCanvas background.

ObjSelectionColor rgb#<n>/<n>/<n>Where: <n> is 0-255.

Color used to indicate aselected object.

PropagationOn {True | False} Specifies whether AlarmSeverity Propagation is On.

Table 10-5 Viewer Configuration File — View PropertiesParameters

Variable Assignable Value Description


10

10.5.1.2 Icon Menus Section

The next section of the Viewer Configuration file contains the Icon Menuparameters. These define the icon popup menu to be displayed for each type oftopology object (topoNode object). For example, the default icon menu entryfor the Hub object type is as follows:

The syntax for a menu description is as follows:

Where:

<object-type-name> is the type of object icon attached to the menu.

<option-label> is the label to be used for the option within the menu.

<absolute-pathname> is the absolute pathname to the executable invoked bythe menu option.

<arguments> are any arguments and options to be passed to the executable.

Menu Hub{"Object Properties..." $EM_HOME/bin/em_oct -host EM_MIS -id EM_UNIQUE_ID"SNMP Browser..." $EM_HOME/bin/em_snmpbrowser -host EM_MIS -id EM_UNIQUE_ID"Data Viewer..." $EM_HOME/bin/em_dataviewer -host EM_MIS -id EM_UNIQUE_ID"Alarm Manager..." $EM_HOME/bin/em_alarmmgr -host EM_MIS -device EM_OBJNAME}

Menu < object-type-name >{“< option-label >” < absolute-pathname > < arguments >}

Viewer 10-71

10

10.5.1.3 Default Activations Section

After the Icon Menus section is the Activations section. This corresponds to theDefault Activations window parameters, accessible through theTools➤Configure➤Default Activations… option. These parameters specify theaction invoked when you double click on an object icon in the Viewer mainwindow.

The format for this section is as follows:

Where:

<keyword> is one of the variable macros described in Table 10-2, Table 10-3,or Table 10-4, above.

<absolute-pathname> is the absolute pathname to the executable invoked bydouble clicking on an object icon.


10.5.1.4 Layers Section

Following the Activations section is the Layers section. The entries in thissection correspond to the layers specified in the Layers window, accessiblethrough the View➤Layers option.

The first entry in this section is of the form:

This assignment specifies whether a background image is to be displayed.

Activations{“< object-type >” {[< keyword >] | [< absolute-pathname > < arguments >]}}

Background: <True | False>


10

For each layer to be displayed, there is a statement of the form:

If no VoLayer statements are included, then all layers are displayed. Thiscorresponds to selecting the Display All Object Layers option in the Layerswindow.

10.5.1.5 Tools Menu Customization Section

When you have used the Tools➤Configure➤Tools Menu… option to add anapplication to the Tools menu, an entry is added at the end of the ViewerConfiguration file. This entry contains the parameter assignments youspecified in the Configure Applications window. The entry has the followingformat:

Where:

<prog-name> is the option label that appears in the Tools menu.

<absolute-path> is the absolute path to the executable.


VoLayer: <layer-name>

Application{name: < executable >path: < absolute-pathname >args: < arguments >}

11-1

Discover 11

11.1 OverviewThe Discover application provides a simple and convenient way to addmanaged objects to the Management Information Server (MIS) database. Thisapplication consists of two functions: the Discover function, and the Monitorfunction.

11.1.1 The Discover Function

Starting from the machine on which it is run, (which might be local to orremote from the MIS machine), Discover finds hosts, routers, networks,subnetworks, links, and Simple Network Management Protocol (SNMP)devices. Upon finding one of these network elements, Discover creates anobject for that element in the MIS.

Overview page 11-1

Starting Discover page 11-2

Discover Properties page 11-7

Monitor Properties page 11-15

Running Discover From the Command Line page 11-20


11

Discover also offers a number of configuration options allowing you to fine-tune the extent and depth of the Discover application’s search activities. TheDiscover configuration options are described in Section 11.3, “DiscoverProperties.”

11.1.2 The Monitor Function

The Monitor function provides a convenient means of regularly updating theMIS topology information. Monitor compares the current MIS networktopology to network resources that it finds while it is active. Monitor can beused to find devices that have been added to the network since Discover waslast run.

The Monitor function also offers a number of configuration options (such astimers and retry parameters) allowing you to customize Monitor’s manner ofoperation. For more information, see Section 11.4, “Monitor Properties.”

11.2 Starting DiscoverStart the Discover application by:

• Selecting the Discover icon in the Application Launcher’s Tool Bar. Refer toChapter 8, “Application Launcher,” for detailed information about theApplication Launcher.

• Typing the em_discover command from the command line. Refer toSection 11.5, “Running Discover From the Command Line,” for detailedinformation.

If you start Discover from the command line, and you are a non-root user, youmight receive a Login window, depending upon whether or not passwordauthentication is turned on. To proceed, enter your password and click OK.Your access to Discover functions depends on the permissions granted to youthrough Access Control. For more information about password authenticationand granting permissions, see Chapter 9, “Access Manager.”

11.2.1 Discover Main Window

After Discover is started, you receive the main window, shown in Figure 11-1.

Discover 11-3

11

Figure 11-1 Discover Main Window


11

The Discover main window consists of a menu bar, the Log window, andaction buttons, which are described in the following subsections.

11.2.1.1 Discover Window Menu Bar

Visible on the menu bar are the Discover, Monitor, and Help buttons:

• Select the Help button for access to online help information.

• Select the Discover button to retrieve a pull-down menu containing anoption for configuring Discover (Refer to Section 11.3, “DiscoverProperties”) and an option to terminate the Discover application.

• Select the Monitor button to retrieve a pull-down menu containing anoption for configuring Monitor (Refer to Section 11.4, “Monitor Properties”).

11.2.1.2 Discover Window Log Window

The display area is where Discover informs you about the status of its query.Here, you will see the various objects listed as they are discovered, as wellvarious messages from the Discover application.

11.2.1.3 Discover Window Action Buttons

The two buttons at the bottom of the Discover window allow you to startDiscover or Monitor as described below:

Start DiscoverInvokes Discover in a way that is determined by the parameters specified inthe Discover Properties window (refer to Section 11.3, “Discover Properties”).You can limit or extend Discover as much as your time and machine resourcesallow. The Start Discover button changes to Stop Discover after you activateDiscover. Selecting Stop Discover terminates a Discover operation.

Note – A key point to remember when using Discover is that the applicationuses the machine from which it is run — not the machine where the MIS islocated — as its starting point. This point might be significant if the MISmachine and the machine from which you run Discover are on differentsubnetworks.

Discover 11-5

11

Start MonitorInvokes Monitor in a way that is determined by the parameters specified in theDiscover Properties window (refer to Section 11.3, “Discover Properties”). Theviews and devices probed when Monitor is actively interrogating the networkis determined by the parameters specified in the Monitor Properties window(refer to Section 11.4, “Monitor Properties”). The Start Monitor button changesto Stop Monitor after you activate Monitor. Select Stop Monitor to terminatethe Monitor function.

11.2.2 How Discover Works

Discover interrogates the network using the following Internet protocols:

• Simple Network Management Protocol (SNMP)

• Internet Control Message Protocol (ICMP)

• Address Resolution Protocol (ARP)

After identifying the local configuration — network and subnet, netmask, hostinterfaces, routing table, and address translation (ARP) table, Discoverinterrogates the network in a two-stage process:

1. The goal of the first (Query) stage of the discovery process is to build aninternal hierarchical model of the network topology. One entry in thishierarchy for each Class A, B, or C network is discovered. Each of thesenetwork entries contains a list of subnets and a list of directly connectednetworks. If the network is not subnetted, then each entry contains a list ofhosts directly connected to this network.

2. The goal of the second (Probe) stage is to find and classify the devices on thesubnets once the network structure has been uncovered. There are severalmethods available at this stage, which the user can select by using theDiscover Properties window (Figure 11-2). See Section 11.3.3.1, “SearchMethod,” for detailed information.

11.2.2.1 Discovery Query Phase

To build the hierarchical model of the network topology, Discover:

1. Accesses the local routing table to find the location of the subnetwork’sdefault router


11

2. Retrieves the router’s routing and ARP tables using SNMP

3. Retrieves the routing and ARP tables from all next hop gateways

4. Leapfrogs from gateway to gateway as it retrieves the routing and ARPtables from each “next hop” gateway

5. Performs a traceroutes operation to determine the number of hops to each“next hop” gateway. Each router that a packet must traverse to reach thatgateway counts as an additional “hop.” The traceroutes operations may alsoreveal gateways that were not uncovered by previous queries.

6. Continues to retrieve routing and ARP tables of “next hop” gateways untilthe “Maximum Hops” count set in the Discover Properties window isreached. By default, Maximum Hops is set to zero and the discovery processis limited to the local subnetwork.

7. Uses SNMP to obtain the routing and ARP tables of any additionalgateways that were uncovered by tracing the route to gateways previouslyuncovered

11.2.2.2 Discovery Probe Phase

For the devices that have been found using the methods described above,Discover attempts to obtain relevant information by:

• Sending an ICMP echo request (ping) to check for reachability of the device

• Determining if the object is an SNMP device and if so, finding out itsinterfaces, system table, iftable, ifstatus, and ARP table

• Using the ipAddrTable to determine the number of interfaces, determiningthe data link protocol of these interfaces (Ethernet, FDDI, Token Ring), andobtaining the MAC addresses

• Testing for a match in the OID to object mapping table

• Testing for a match in the sysDescr to object mapping table

Once the above tests are completed and the relevant information is obtained,Discover creates an object for the device in the MIS (assuming that the objectdoes not already exist). The information obtained from the tests is used to setthe attributes of the object.

Discover 11-7

11

11.2.3 Discover and Network Security

By default, Discover probes the network by using the following ports:

• 161—Discover uses this port to communicate with the SNMP daemon(snmpd) on a remote device.

• 32768+666—Discover uses this port to determine the hop distance to adevice.

Note – If the “Stop at Gateways” option is used, port 32768+666 is not probed.For more information, see Section 11.3, “Discover Properties.”

• 80, 8080—If the command line option -www is used, Discover probes theseports to determine whether or not a WWW server is running on themachine.

11.3 Discover PropertiesSelect Discover ➤ Properties to retrieve the Discover Properties window(Figure 11-2).


11

Figure 11-2 Discover Properties Window

Discover 11-9

11

The various fields and parameters within the fields of the Discover Propertieswindow allow you to determine how Discover operates.

11.3.1 ICMP/SNMP Field

This field contains options allowing you to configure Discover’s search fordevices using ICMP and SNMP devices. It also allows you to specify a defaultproxy

11.3.1.1 SNMP Read Community

Discover will try to access the SNMP information on a device using the SNMPread community string(s) specified in this field. Up to five SNMP readcommunity strings can be specified, delimited by a colon. For example, if youspecify “public:floor2” as the SNMP read community strings, Discover tries toaccess the SNMP information by first using “public”, then “floor2”. The defaultDiscover read community string is “public”.

11.3.1.2 SNMP Write Community

Only one SNMP write community string can be specified. The default Discoverwrite community string is “private”.

Note – The SNMP Write Community option is used only to configure an optionin the MIS—Discover does not send any SNMP SET requests.

You can change the write community string for a device using the ObjectConfiguration Tool. For more information, see Chapter 19, “ObjectConfiguration Tool.”

11.3.1.3 SNMP Timeout

This parameter determines the number of seconds for which Discover tries tocontact an SNMP device. The default setting for this field is 3.


11

11.3.1.4 SNMP Retries

Used primarily for querying routers, this parameter determines the number oftimes Discover tries to contact an SNMP device. ARP and routing tables areoften large and sometimes require multiple retries to obtain complete tables.The default value for this field is 1.

11.3.1.5 ICMP Retries

This parameter determines the number of times that Discover tries to contact adevice using ICMP (ping). The default value for this parameter is 1.

11.3.1.6 ICMP Timeout

This parameter determines the number of seconds that Discover tries to “find”an element using ICMP (ping). If your network is very busy, or you havespecified a large hop count which causes Discover to ping devices that are faraway, you might want to increase this value. However, increasing this valueslows down the discovery process. The default value for this field is 1.

11.3.1.7 Hop Count

The Hop Count is a measure of how far Discover will extend its search. Forany given route from the machine running Discover (or from the subnetworkspecified in the Network parameter), this parameter specifies the maximumnumber of routers that the packets sent by Discover will traverse. The defaultfor this parameter is zero hops, which means searches are restricted to the localsubnetwork. Specifying -1 in this field causes Discover to not limit its search.

Warning – Depending on the size of your network, setting the Hop Count toany value above zero can result in very long searches, especially if you haveselected the serial pinging option. A possible strategy would be to limit theObjects to Discover to subnets, links, and routers for searches with a hop countgreater than 0.

Discover 11-11

11

11.3.1.8 Default Proxy

SunNet Manager (SNM) RPC-based agents and proxy agents deployed ondevices in your network can be used by Solstice EM as part of your strategy formanaging network resources. The resource may be a machine, a component ina machine (such as a router interface card), or some other resource. The SNMagent may be local to or remote from that resource. For more information, seethe “Device Management Using RPC Agents” chapter in the Solstice EnterpriseManager Administration Guide.

The Default Proxy field allows you to specify the name of a machine you wantto act as a proxy and perform the actual network polling. Any machine withthe desired RPC-based SunNet Manager (SNM) agent can be specified. Thedefault value for this field is localhost, meaning that the polling will be done bythe agent on the local machine.

11.3.2 Objects Field

This field allows you to select which object(s) you want to discover. All Objectsis the default option, causing all the other options to be grayed out. If you donot want to discover all objects, click once on the All Objects toggle button, andthe other options will become active. The other options are:

• Networks/Subnets—Collections of subnetworks or individual subnetworks.No probing of individual devices will be carried out.

• Routers—Device that is capable of forwarding and actually forwards IPpackets between two or more networks. A router’s ipForwarding is set toGATEWAY, indicating that it actually performs routing. When Discoverfinds a router, it associates that router with the IP address of the firstinterface it finds on that machine. If this option is selected, Links andNetwork/Subnets is also selected.

• Hosts—Device that does not route IP packets to any other networks that theone it is connected to. A host’s ipForwarding is set to HOST. If this option isselected, Network/Subnets is also selected.

• SNMP Devices—Systems or other devices running SNMP. If this option isselected, Network/Subnets is also selected.

• Links—Connections between a router and a subnetwork. If this option isselected, Routers and Network/Subnets are also selected.


11

The reason that some types of objects are necessarily discovered withothers—for example, routers with networks/subnets—is that in the MIS,certain types of managed objects must have parent-managed objects.

For a large network, it is recommended that you start by:

• Discovering routers, networks, and links

• Setting the hop count to 2

• Setting the SNMP timeout to 10 seconds

• Setting the ICMP timeout to 10 seconds

After discovering all routers, networks, and links up to 2 hops away, it isrecommended that you proceed to discover each subnet. One good method ofdoing do is to specify a proxy agent.

11.3.3 General Field

By allowing you to specify a search method and view creation, this field allowsyou to further customize the discovery process

11.3.3.1 Search Method

You can specify one of the following methods for finding objects:

• Default—Discover uses a combination of Address Resolution Protocol(ARP) and Ping. First, the ARP tables of the gateways are used to update thedatabase topology. Then, ICMP echo packets (ping) are sent to locatepotential devices for the missing IP addresses not found in the gateway ARPtables. This is the default search method.

• Serial PING—Discover access the interface and routing tables to findnetworks and subnets. It then sends an ICMP echo packet (ping) to eachnetwork and subnet to find all devices.

• ARP—Discover pings only those devices on each subnet listed in the routerARP tables, obtained by SNMP. Each such device is sent an ICMP echorequest to determine whether it is available. This method is not particularlyuseful for discovering remote networks.

Discover 11-13

11

11.3.3.2 View Creation

This field allows you to configure a new view under which the discoveredobjects will be placed:

• Hierarchy—Discover places all objects hierarchically under the specifiedview. This is the default setting.

• Flat—No network/subnet/segment hierarchy is created. Every devicefound will be in the specified view.

Since selecting the Flat option causes all objects to be placed under a singleview, it is not recommended that you use this option for large networks. Thetopology will not be created correctly if, for example, you run Discover usingthe Flat option, then later run it using the Hierarchy option.

If you want to create a view containing a single object type, you should runDiscover using the Hierarchy version, then use the Gather window in theViewer to create a new view in which you can place the objects. For anexample on how this is done, see the “Populating the MIS” chapter in theSolstice Enterprise Manager Administration Guide.

11.3.3.3 Default View

This field should contain the name of the default view under which you wantthe discovered objects to be placed.

11.3.3.4 Network

This field should contain the name or subnetwork number—as specified in anNIS map, NIS+ table, or the /etc/networks file—that identifies thesubnetwork on which Discover is to function. By default, Discover uses thenetwork number of the local machine. When specifying a network number, besure to enter a value for each byte within the number. For example, specify thezero, as in 129.144.41.0 , not 129.144.41 .

Note – If you enter a network name or number outside of the localsubnetwork, the Discover function limits its search to the subnetwork youspecify. In effect, you limit Discover to a zero-hop search.


11

11.3.3.5 Netmask

This field should contain the network mask—as specified in an NIS map, NIS+table, or the /etc/netmasks file—used in the network(s) on which Discoveroperates. By default, Discover uses the netmask number used on the localsubnetwork. Enter the netmask number in hexadecimal (preceded by 0x ) ordotted decimal notation (for example, 255.255.255.0 ).

The Netmask parameter is intended for use in conjunction with the NetName/Number parameter. Use it when you want a discovery to occur in asubnetwork other than the local subnetwork and the netmask for thatsubnetwork is different from the local netmask.

Warning – The netmask and network names must match the actual networkconfiguration.

11.3.4 Gateways

This field allows you to enter a list of specific gateways to be queried as part ofthe discovery process. The specified gateways will be queried first during thediscovery phase, before the rest of the network. To query only the specifiedgateways, click on the Stop at Gateways toggle button. This is the quickestmethod of discovering objects on your network.

11.3.5 Agent Mapping

SunNet Manager (SNM) RPC-based agents and proxy agents deployed ondevices in your network can be used by Solstice EM as part of your strategy formanaging network resources. The resource may be a machine, a component ina machine (such as a router interface card), or some other resource. The SNMagent may be local to or remote from that resource. For more information, seethe “Device Management Using RPC Agents” chapter in the Solstice EnterpriseManager Administration Guide.

The proxy Agent Mapping field allows you to select which RPC-based SNMagents should be configured for each object that is discovered. If you select anagent from this field, then an agent object will be created.

Discover 11-15

11

When you finish specifying the Discover configuration parameters, select theApply button to accept your input and the parameters for the next time youperform a discover operation. Selecting the Cancel button dismisses theDiscover Properties window without implementing any changes. Selecting theOK button applies your selected configuration values and closes the DiscoverProperties window. For online assistance, click on the Help button.

11.4 Monitor PropertiesSelect Monitor ➤ Properties to retrieve the Monitor Properties window (seeFigure 11-3).

The Monitor Properties window provides configuration options (such as timersand retry parameters) that allow you to customize the Monitor’s manner ofoperation.


11

Figure 11-3 Monitor Properties Window

Discover 11-17

11

The various parameters in the Monitor Properties window are described below.

11.4.1 Objects to Monitor

This field allows you to instruct Monitor to search only those networks orsubnetworks corresponding to the containers you specify.

11.4.1.1 Monitor These Containers Only

To add/specify a container, type the container name in the field immediatelybelow the Monitor These Containers Only window, then click on the Addbutton. To remove a container from the list, select it, then click on the Deletebutton.

Note – Container names must be specified; IP addresses are not allowed.

11.4.1.2 Ignore These Objects

This parameter instructs Monitor to avoid pinging specified devices. Toadd/specify a device which Monitor should ignore, type the device name inthe field immediately below the Ignore These Objects window, then click onthe Add button. To remove a device from the list, select it, then click on theDelete button.

11.4.2 General

The following subsections describe parameters in the General field whichallow you to further customize how the Monitor function operates.

11.4.2.1 Object Down Timeout

This parameter allows you to specify the number of minutes that an object isunreachable before a Communications Alarm is sent. Click on the up arrow toincrease this value, or the down arrow to decrease this value. The default is 30minutes.


11

11.4.2.2 Time Between Cycles

This parameter allows you to specify the period of time (in minutes) betweeneach run of monitor. Click on the up arrow to increase this value, or the downarrow to decrease this value. The default is 15 minutes.

11.4.2.3 Holding Container

This parameter allows you to specify the name of container in which you wantnewly discovered objects to be placed. The default is “Root,” which means thatdevices are added to the topology in the specified container as they are found.You should use this parameter if you are concerned with the layout of yourtopology.

11.4.2.4 No Response Event

When Monitor finds that a certain object is unreachable, it can generate aCommunications Alarm of a specified perceivedSeverity. By default, thisoption to generate alarms is off.

Select the On toggle button to activate this feature, then click on the buttonimmediately to the right of the On toggle button to select a perceivedSeverity.The available severities are:

• Critical

• Major

• Minor

• Warning

When the Monitor finds a previously unreachable host reachable, it generates aCommunications Alarm with perceivedSeverity set to “Cleared.”

11.4.3 Log Information

Monitor’s logging function allows you to keep track of the monitor process,export this information to a file, and send the file electronically to a specifiedrecipient.

Select the On toggle button to activate Monitor’s logging function. Todeactivate Monitor’s logging function, click the Off toggle button.

Discover 11-19

11

11.4.3.1 Log File

To save the log information to a file, specify the file name in the Log File field.By default, the file is placed in /tmp/em_discover_< pid>.log , where <pid>is the process ID of the Discover process.

11.4.3.2 Mail To

To electronically mail the Monitor log file to someone at the completion of eachMonitor cycle, specify the recipient’s electronic mail address in the Mail Tofield. Make sure that you enter a valid username!

11.4.4 Timers

This field provides options allowing you to specify when Monitor shouldoperate.

11.4.4.1 Start Time

This option allows you to specify a time to start Monitor. Click on the button tothe right of “Start Time” and select a time from the resulting pull-down menu.Then, click on either the AM or PM toggle buttons. If you specify a start timein the future, Monitor will not start automatically. You must click on the StartMonitor button to start the monitor process.

11.4.4.2 Start Date

This option allows you to specify a date to start Monitor. The date must be inthe format MM/DD/YY. The default is today’s date.

11.4.4.3 Stop Time

This option allows you to specify a time to stop Monitor. Click on the button tothe right of “Stop Time” and select a time from the resulting pull-down menu.Then, click on either the AM or PM toggle buttons.


11

11.4.4.4 Stop Date

This option allows you to specify a date to stop Monitor. The date must be inthe format MM/DD/YY. The default is one week from today.

11.4.4.5 Run Weekly

This options allows you to run Monitor once a week on the specified day. Clickthe On toggle button, then click on the button to the right of the On togglebutton, and select a day of the week from the resulting pull-down menu.

To disable this feature, click on the Off toggle button.

When you finish specifying the Monitor configuration parameters, select theApply button to put your selections into effect for the current Discoverapplication session. Selecting the OK button also puts your selections intoeffect for the current Discover application session, but also dismisses theMonitor Properties window. Select the Cancel button to dismiss the MonitorProperties window without implementing any of the changes specified in theMonitor Properties window. For online assistance, click on the Help button.

11.5 Running Discover From the Command LineStart Discover from the command line as follows:

The available command line options are briefly described below.

-arpCauses Discover to use a combination of ARP Tables and ICMP echorequests (pinging) to discover devices on subnets. By default, Discover usesserial pinging of the host addresses on subnets, which can be quite time-consuming.

hostname% em_discover [options]

Discover 11-21

11

-cr < string> [:< string>]Allows you to specify up to five SNMP read community strings to limit theDiscover function’s search to only those devices that have the specifiedcommunity names. The default is “public.” Use a colon to separate multiplecommunity strings. Using multiple community strings can significantlyincrease the time of the discovery process.

-cw <string>Allows you to specify the SNMP write community strings to limit theDiscover function’s search to only those devices that have the specifiedstring. The default is “private.” Only one write community string can bespecified.

-device < device_name>Discover only the specified device.

-g [only] <gateways>Allows the use of the specified gateway(s) in the discovery process. You canenter multiple gateway names, separated by a colon. If the keyword “only”is entered, Discover skips the network probing phase and probes only thenetworks found at the listed gateways. This method is the fastest.

-host <hostname>Allows you to specify the name of the host machine where the MIS isrunning

- hop <n>Allows you to specify the maximum number of hops from the manager thatDiscover will follow. 0 is the default, which restricts Discover’s search to thelocal subnetwork. Enter -1 to instruct Discover to not limit its search.

-mask <n>Allows you to specify the netmask to be used for discovery purposes

-n et <network>Allows you to specify a specific subnetwork or non-subnetted network todiscover, thus limiting the search. The maximum hop count for asubnetwork other than the local one is 0.


11

-objects <objects>Allows you to specify the types of objects you want to discover. Theacceptable values are: snmp, host , network , router , and link . Multiplevalues must be separated by a colon. By default, Discover finds all types ofobjects. Certain types of objects are necessarily discovered in conjunctionwith other types, as described earlier in the “Objects Field” section.

-pbCauses Discover to use a broadcast method of pinging in probingsubnetworks

Note – The -pb option creates a heavy network load and is not recommendedfor use with Monitor or for searches with -hop greater than 0.

-pfn <num>Allows you to specify the maximum number, <num>, of outstandingsimultaneous pings per interval specified by -pft option. The default valueis 10.

-pfr <num>Allows you to specify the number of times Discover tries to contact a deviceusing ICMP (ping) when the default serial ping method is used

-pft <seconds>Allows you to specify the frequency between transmissions of ICMP echorequests (in seconds) when the default serial ping method is used

-p r <num>Allows you to specify the number of times Discover tries to contact a deviceusing ICMP (ping). Increase this value for very busy or long-haul networks,.However, increasing this value slows down the discovery process.

-r <from:to>Allows you to specify a range of host addresses to ping for eachnetwork/subnet specified. The range can be specified in the form<IPaddress1>:<IPaddress2>.

-S <n>Allows you to specify the number of tries when sending SNMP requests todevices. Increase this value for a very busy or long-haul network.

Discover 11-23

11

-TBrings up the Discover application’s Graphical User Interface (GUI)

-t <n>Allows you to set the ICMP (ping) timeout value to <n> seconds

-flatCreates objects in a flat hierarchy.

-waitInstructs Discover to wait for a platform connection at start-up.

-wwwNotify when discovered device is a WWW server (uses ports 80 and 8080).

11.5.1 Monitor Command Line Options

Start Monitor from the command line as follows:

The -M parameter starts the Monitor function. The optional parameters forstarting Monitor from the command line are as follows:

-contain < container>Instructs Monitor to place all newly discovered objects into the specifiedcontainer.

-ct < time>Specify the amount of time (in minutes) between each time Monitor is run.

-h < holding_area>Specify the name of the holding area into which all newly discovered objectsare placed.

-fc <container-name>Limits Monitor’s search operations and reachability testing to devices in thecontainer specified by <container-name>. Multiple container names can bespecified, separated by a colon.

hostname% em_discover -M [options]


11

-i <device-name>Ignores the devices specified in <device-name>. Multiple device names can bespecified, separated by a colon. Use this option to instruct Monitor not toping for devices that have been taken down or removed from the network,but which are still in the MIS database.

-lhActivate the log monitor history feature.

-lf <filename> Specify the name of the log monitor history file.

-m <address>Mail log monitor history file to specified address.

-start <hh:mm>Specify the start time in the format hh:mm.

-stop <hh:mm>Specify the stop time in the format hh:mm.

-startd <mm:dd:yy>Specify the start date in the format mm:dd:yy.

-stopd <mm:dd:yy>Specify the stop date in the format mm:dd:yy.

-wRun Monitor weekly.

11.5.2 Debugging Options

Debugging options are available with Discover only at the command line, andare always printed to standard output:

The following sets of debugging options are available with Discover:

• Options allowing you to receive detailed information about the discoveryprocess that is being executed, and run a full discover process and thusestablish a connection with the MIS:

hostname% em_discover -D [options]

Discover 11-25

11

-D nPrints debugging information about the discovery process in aformat that is understandable to the average user

-D ePrints debugging information about the discovery process in aformat that assumes Internet-specific expertise

• Options allowing you to start specific software modules that arecomponents of Discover, but will have no effect on the MIS itself as no MISconnection will be made:

-D cStarts Discover’s Configuration module, which prints informationabout the host on which Discover is running, such as local routingtable, ARP table, interfaces, default routers, network number, subnetnumber, and netmask

-D s <hostname>Starts Discover’s SNMP module, which takes <hostname> as itstarget host, does a one-time SNMP query of the specified device,and prints the information to standard output

-D t <hostname>Starts Discover’s Traceroutes module, which executes thetraceroutes code with <hostname> as target, and prints the routeto the specified host along with the gateways to get there to thestandard output.


11

12-1

Data Collector 12

12.1 OverviewThe Data Collector enables you to configure Data Collection Entry objects. TheData Collection Entry objects store the information necessary to perform therequests, and the Data Collector daemon performs the requests based on thoseobjects.

There is no limit, other than system resources, on the number of concurrentdata requests.

12.1.1 Request Objects

A request object is essentially a definition of the type of data for which to poll,the polling frequency, and which managed objects residing on the specifiedMIS(s) to poll. You can create these object definitions by using the DataCollector Create window, described in detail further on in this chapter.

Overview page 12-1

Starting the Data Collector page 12-3

Using Data Collector Windows and Menus page 12-4

Data Collector GDMO Classes page 12-14


12

12.1.2 The Data Collector Daemon (em_datad )

The Data Collector daemon (em_datad ) performs data collection requests forthe Data Collector, based on the contents of Data Collection Entry object.

Note – Since em_datad performs requests based on Data collection Entryobjects, there is no feature level security for the daemon.

The Data Collector daemon performs the following functions:

• After you have created a Data Collection Entry object, em_datad schedulesa data request for that object. When you create the object, you can specifythe starting and stopping date and times for the request. The daemon thenautomatically starts and stops the request at the specified times.

• When you stop or delete any Data Collection Entry object, the daemon stopscollecting data from that object instance.

• When you restart a stopped object instance, the daemon resumes collectingdata from that object instance as long as the information requested by theData Collection Entry object still exists in the MIS.

• The data that is retrieved is based on the object instances and attribute listcreated in the Data Collector. You can select any number of objects instancesand specific attributes for each of those instances.

• The daemon writes all retrieved data for a request to the file you specifiedwhen you created the Request Object.

• By default, when a log file reaches the specified maximum file size, thedaemon begins overwriting the file with new data. If you disable wrapping,the daemon simply stops writing to the file when the maximum file size isreached.

• Any application can access the log files to display or utilize request data.

• When the request state is locked, the daemon stops the request from loggingdata to the log file. The locked state takes precedence over the Start and Stoptimes.

• When the request state is unlocked, the daemon can start and stop therequest at the specified times.

Data Collector 12-3

12

12.2 Starting the Data CollectorYou can start the Data Collector in either of two ways:




12.2.1 Starting the Data Collector from theApplication Launcher

You can start the Data Collector by selecting the Data Collector icon in theApplication Launcher main window. To start up the Application Launcher,enter the following command at the operating system prompt:

The optional -host <hostname> parameter allows you to specify the name of aremote machine where the MIS is running.

12.2.2 Starting the Data Collector From theCommand Line

You can also invoke the Data Collector by entering this command at theoperating system prompt:

The optional parameters are as follows:

host% em [-host < hostname>] &

hostname% em_datacollector [-help] [-host < hostname>] &

Option Description

-help Print list of options (with descriptions) for theem_datacollector command.



12

12.3 Using Data Collector Windows and MenusWhen you first invoke the Data Collector, the main window appears asillustrated in Figure 12-1:

Figure 12-1 Data Collector Main Window

The Data Collector main window contains the following components:

• Menu bar menu buttons:• File• Object• Help

• Data Collection display area

• Status line

These are described in the sections below.

Data Collector 12-5

12

12.3.1 File Menu

Select File from main window menu bar to see the File pulldown menu. Thismenu contains the following option:

ExitSelect File➤Exit to quit the Data Collector application. All data collectionsrequests continue to run for the specified time.

12.3.2 Object Menu

Select Object from the main window menu bar to see the Object pulldownmenu. This menu contains the following options:

• Create...

• Edit...

• Start

• Stop

• Delete

These are described in the following sections.

12.3.2.1 Create...

Select Object➤Create... to see the Create window as illustrated in Figure 12-2:


12

Figure 12-2 Create Window

Use this window to create a request object. The Create window contains thefollowing elements:

Request ObjectThis section of the Create window contains the following options and fields:

Object ListThis displays a list of the objects in the current request object.

Data Collector 12-7

12

Object:In the Object field, enter the name of the object you want to add to therequest object.

AddClick on Add to add the new or selected object to the request object.

DeleteClick on Delete to delete the selected object from the request object.

Object Browser....Click on the Object Browser... button in the Request Object section of theCreate window to see the Object Browser window as illustrated inFigure 12-3:


12

Figure 12-3 Object Browser Window

The Object Browser window displays a selection list of all currentlymanaged objects in the MIS. The window contains the following elements:

• Folder Icons — Click on a folder icon to see the contents of that object. Clickon the item label to select it.

• Add — After selecting an item, click on Add to add it to the object list anddismiss the Object Browser window.

• Close — Select Close to dismiss the Object Browser window.

Data Collector 12-9

12

Object Attributes ListThis area of the Create window displays a list of attributes for the selectedobject.

Attribute:In this field of the Create window, enter an attribute name for the selectedobject.

AddClick on Add to add the selected attribute to the object attribute set.

DeleteClick on Delete to delete the selected attribute from the object attribute set. Adialog box will appear prompting you to confirm your delete request.

Object Attributes....Select Object Attributes in the Request Object section of the Create window tosee the Attribute List window as illustrated in Figure 12-4:


12

Figure 12-4 Attribute List Window

This window displays the attributes of the object selected in the object list.Use this window to add an attribute to the object attribute list.

The Attribute List window contains the following elements:• Attribute List display area — This displays a list of the existing attributes

for the selected objects. Click on an item in this list to select it. You canselect multiple items.

• OK — Click on OK to add the selected attribute to the object attribute listand dismiss the Attribute List window.

Data Collector 12-11

12

• Apply — Click on Apply to add the selected attribute to the objectattribute list. The Attribute List window remains.

• Close — Click on Close to dismiss the Attribute LIst window.

PropertiesThe Properties section of the Create window contains the following fields:

Request Name:Enter the name of the request object in this field.

Poll Interval:Select the polling interval in seconds for the request. Use the up/downarrow buttons to increase/decrease the value in this field.

File Name:Enter the name of the log file in this field.

Max File Size:Use the up/down arrow keys to increase or decrease the maximum file sizefor the logfile. If wrapping is enabled, then when the file size reaches thisvalue, log data begins wrapping to the top of the file.

Log Format:In this field, specify the format to use for log files. Select one of thefollowing:

• EM• SNM

File Wrapping:By default, when a log file reaches the specified Max File Size, the log datastarts wrapping. To turn off this feature, select No in the File Wrapping:field.

Write Document Name:Select Yes or No to specify whether to log the document name.


12

Write Attribute Name:Select Yes or No to specify whether to log the attribute name.

Start Time:In this field, enter the desired start time for the request and select AM orPM.

Start Date:In this field, enter the desired starting date for the request. The format forthis value is: mm/dd/yyyy.

Stop Time:In this field, enter the time at which you want the request terminated, andselect AM or PM.

Stop Date:In this field, enter the date at which the request should be terminated. Theformat for this value is: mm/dd/yyyy.

Command ButtonsAt the bottom of the Create window there are a series of command buttons forapplying or canceling your entry. These are:

CreateClick on Create to create the specified Request Object and dismiss the Createwindow.

ApplyClick on Apply to create the Request Object without dismissing the Createwindow.

CancelClick on Cancel to dismiss the Create window without creating an object.


12

12.3.2.2 Edit...

Select Object➤Edit... from the main window menu bar to see the Edit window.This window is identical to the Create window (see Section 12.3.2.1, “Create...,”above) except that the Create button is replaced by the Modify button.

Note – The Edit window allows you to change any field except the RequestName.

To edit a Request Object, do the following:

1. Select the object to be edited from the main window Request Object list.

2. Select Object➤Edit.The Request Object information for that object appears in the Edit form.

3. Enter your modifications.

4. Click on the Modify button to implement your changes.

12.3.2.3 Object Control Commands

The remaining options in the Object menu are Request Object controlcommands. These are as follows:

StartSelect Object➤Start to start the selected Request Object.

StopSelect Object➤Stop to stop the selected Request Object.

DeleteSelect Object➤Delete to delete the selected Request Object.


12

12.4 Data Collector GDMO ClassesThe following GDMO classes are defined for Data Collector objects:

• dataCollector — This is defined as the container class for Data CollectionEntry objects.

• dataCollectorEntry — This is defined to represent data collectionrequests.

Both object classes are defined as persistent.

12.4.1 The dataCollector GDMO class

The dataCollector object is defined by the GDMO class shown inTable 12-1.

Table 12-1 dataCollector GDMO Class

dataCollector MANAGED OBJECT CLASS

DERIVED FROM "Rec. X.721 | ISO/IEC 10165-2 : 1992" : top;

CHARACTERIZED BY

dataCollectorPackage;

REGISTERED AS { em-data-collector-class 1 };

dataCollectorPackage

BEHAVIOUR dataCollectorPackageDefinition BEHAVIOUR DEFINED AS

!The managed object class represents a data collector object!

ATTRIBUTES

dataCollectorId GET,

"Rec. X.721 | ISO/IEC 10165-2 : 1992": administrativeState;

NOTIFICATIONS

objectCreation,

objectDeletion,

attributeValueChange

;


12

12.4.2 The dataCollectorEntry Object GDMO Class

The dataCollectorEntry object is defined by the GDMO class in Table 12-2.

Table 12-2 dataCollectorEntry GDMO Class

dataCollectorEntry MANAGED OBJECT CLASS

DERIVED FROM "Rec. X.721 | ISO/IEC 10165-2 : 1992" : top;

CHARACTERIZED BY

dataCollectorEntryPackage;

REGISTERED AS { em-data-collector-class 2};

dataCollectorEntryPackage

BEHAVIOUR dataCollectorEntryPackageDefinition BEHAVIOUR DEFINED AS

!The managed object class represents a data request!

ATTRIBUTES

dataCollectorEntryId GET,

requestInterval GET-REPLACE,

requestInfo GET-REPLACE,

requestStart GET-REPLACE,

requestStop GET-REPLACE,

logFile GET-REPLACE,

logFileMaxSize GET-REPLACE,

requestState GET-REPLACE,

"Rec. X.721 | ISO/IEC 10165-2 : 1992": administrativeState;

NOTIFICATIONS

objectCreation,

objectDeletion,

attributeValueChange

;


12

12.4.2.1 The RequestInfo Attribute

The syntax for the requestInfo attribute is shown in Table 12-3.

Table 12-3 requestInfo Attribute Syntax

RequestInfo ::= SET OF RequestData

RequestData ::= SEQUENCE {

objects ObjectInstance,

attrs SET OF AttributeId

}

13-1

Log Manager 13

13.1 OverviewThe Log Manager enables you to create, modify, and delete log objects. A logobject is a software entity that collects records (called log records) of eventnotifications. Agents create event notifications when they detect a change inthe state of a managed object. The agents can be configured to forward thenotifications to the EM Management Information Server (MIS), where a recordof the notification (a log record) might be appended to a log object, if the eventpasses the discriminator or is discarded.

You can browse log records at any time using the Log Viewer application. Forinformation on using the Log Viewer see, Chapter 14, “Log Viewer.”

Overview page 13-1

Using the Log Manager page 13-4

Defining the Discriminator Construct page 13-15

Sample Discriminator Constructs page 13-20

Log Manager Configuration File page 13-23


13

An MIS can have any number of log objects. As shipped with EM, the MIS hasa single log object, which is visible when you invoke the Log Manager. This logobject, AlarmLog, collects log records for all OSI-standard and Nerve Centeralarms and can satisfy the needs of many customers. Log Manager makes iteasy to create new log objects as you need them.

A key component of a log object is something called a discriminator construct.This is a CMIS filter that determines whether a log record is created under alog object. A log record is defined for each event notification. This mappingfrom event notification to log record is stored in the MIS atsubsystemID=”EM-MIS”/listname=”event2ObjectClass” in attributeevr2oclist .

Each notification has an attribute describing its notification type. Commonnotification types are shown in Table 13-5, but the set is open-ended, requiringonly that each new type have a registered OID.

Refer to Section 13.3, “Defining the Discriminator Construct,” for detailedinformation about discriminator constructs.

Every notification the MIS receives is passed to each log object that has beencreated. Each log object then applies its own discriminator construct to decidewhether to keep a record of the notification or ignore it.

13.1.1 Attributes of a Log

Each log object has the attributes shown in Table 13-1. Some attributes can bemodified, as indicated in the description column. All of these attributes areaccessible through the Log Manager.

Table 13-1 Log Object Attributes


logId Each log object is identified by its FDN (FullyDistinguished Name) in the EM MIS’s ManagementInformation Tree (MIT).

discriminatorConstruct A test that decides whether to log an arriving notification(can be modified).

maxLogSize Each log object has a maximum size and an attribute thatindicates whether its maximum size has been reached. Amaximum size set to zero indicates no limit. Size isexpressed in octets (can be modified).

Log Manager 13-3

13

A notification record is logged only if all the following criteria are met:

Note – Throughout the remainder of this chapter, the terms “log” and “logobject” are used interchangeably.

• The notification is acceptable to the log object’s discriminator.

• The log object has the capacity to receive the record or permits overwriting.

• The log object is unlocked.

If a notification is acceptable to the discriminator constructs of several logobjects, it is recorded in each of them.

Note – Creating multiple logs with overlapping criteria has the potential forstoring duplicate copies of notifications.

13.1.2 Log Records Generated by RequestDesigner Actions

One of the condition statements available in the Request Condition Language(RCL) is alarm() , which generates a Nerve Center alarm. The log objectshipped with Enterprise Manager, by default, creates log records for NerveCenter alarms. As a result, when you make a request based on a requesttemplate that uses alarm() , the default log object creates log records uponeach invocation of alarm() (alarm() and the other RCL alarm-logging

currentLogSize Number of octets the log object and its records nowoccupy in the MIS (reportable but cannot be modified).

numberOfRecords The number of log records under the log object (reportablebut cannot be modified).

logFullAction(wrap/halt)

When the log object is full, it either starts to overwrite theoldest records or stops accepting new records, according tothe value of this attribute (can be modified).

administrativeState(locked/unlocked)

When set to locked, the log object cannot be written to.When set to unlocked, allows the log object to be writtento (can be modified).

Table 13-1 Log Object Attributes (Continued)



13

functions are described in the “RCL Functions” chapter in the Solstice EnterpriseManager Administration Guide. In the Log Manager, you can modify thediscriminator construct for the default log object to filter out these alarms.Alternatively, you can, for example, create a new log object that accepts onlyNerve Center alarms.

13.2 Using the Log ManagerBefore using Log Manager, decide on the types of event notifications you wantto log. The AlarmLog log object that is shipped with Enterprise Manager mightbe sufficient for your needs. To create a new log object, use the Log Manager toname the log object and fill in the modifiable attributes described in Table 13-1.

All of the log attributes are simple, except for the discriminator construct.Specify the discriminator construct using the ASN.1 syntax for a CMIS Filter.The easiest way to create a discriminator construct is to copy a construct froman existing log and paste it into the discriminator construct field in the LogManager’s Log Creation window, where you can modify the construct to suityour needs.

Discriminator constructs are discussed in detail, with examples presented, inSection 13.3, “Defining the Discriminator Construct.

13.2.1 Starting the Log Manager

The Log Manager may be started by:

• Selecting the Log Manager icon in the Application Launcher window

• Selecting Tools ➤ Log Manager in other EM applications (for example, theViewer or Log Viewer)

• Entering the following command from the command line:

Log Manager 13-5

13

Note – Before invoking the Log Manager from the command line, be sure thatthe $XFILESEARCHPATH environment variable is set. If you installedEnterprise Manager in the default location, it should point to/opt/SUNWconn/em/config/%N . If this environment variable is not set, thefonts, colors, and backgrounds may not be displayed correctly.

If you start the Log Manager from the command line, and you are a non-rootuser, you might receive a Login window, depending upon whether or notpassword authentication is turned on. To proceed, enter your password andclick OK. Your access to the Log Manager functions depends on thepermissions granted to you through Access Control. For more informationabout password authentication and granting permissions, see Chapter 9,“Access Manager.”

The optional parameters of the em_logmgr command are described inTable 13-2.

Table 13-2 Options for the em_logmgr Command

Before starting, the Log Manager looks for the.em_logmgr.cf configurationfile in your home directory. If this file is not found, the default Log Managerproperties are used. The format of the configuration file is discussed inSection 13.5, “Log Manager Configuration File.”

hostname% em_logmgr [-host < hostname>] [-logobj | -logrec < fdn>]

Option Description

-help Print list of options (with descriptions) for the em_logmgrcommand.

-host < hostname> Specify the <hostname> of a remote MIS. You can specifyan IP address as the <hostname>.

-c < filename> Specify the <filename> of the configuration file.

-logobj < fdn> Display the log objects of the MIS specified in <fdn> in themain window summary table.

-logrec < fdn> Same as -logobj . This option is for compatibility with theLog Viewer application.


13

After starting the Log Manager, the Log Manager main window, shown inFigure 13-1, appears.

Figure 13-1 Log Manager Main Window

The column below the logId heading in the Log Manager main windowcontains a list of the log objects the MIS knows about. The other fields displayinformation on various log attributes for a given log object. These attributes aredescribed in Table 13-1 and are discussed in the subsections that follow.

You can use the mouse to adjust the size of the rows or columns in the table.Place the cursor on the line in a row or column where you want to make anadjustment; the cursor changes to an arrow. Hold down the left mouse buttonand drag the cursor until the row or column is the size you want.

13.2.1.1 File Menu

Selecting the Log menu displays the following pull-down menu options:

Log Manager 13-7

13

PropertiesSelect File ➤ Properties to retrieve the Properties window, shown inFigure 13-2, which is used to choose the locations from which the log objectsare to be read.

Figure 13-2 Properties Window

From this window, you can:

• Specify the name of a remote MIS, which will be shown as an additionalFDN in the Available FDNs list. The logs from the specified MIS will also beavailable for you to see.

• Specify the location(s) from which the Log Manager will read the log objectsby selecting it in the Available FDNs list and clicking on the Display button.

Once you specify the location(s), click either the OK or Apply buttons at thebottom of the window, and the log object information will be displayed in theLog Manager main window table.


13

Import FileSelect File ➤ Import File to read exported log records. This brings up a fileselection window, from which you can:

• Select the desired file from the list

• Enter the name of the file in the Selection field.

The file must be in the historical log format specified in Chapter 5, “LogManagement.”

Export to FileSelect File ➤ Export to File to save the log records to a file. This brings up a fileselection window, from which you can

• Select the path and file name to which you want to save the log records

• Enter the path and file name of the file in the Selection field.

The records are stored in the historical log format specified in Chapter 5, “LogManagement.”

This option is grayed out unless one or more of the log objects in the mainwindow is selected.

PrintSelect File ➤ Print to display the Print window:


Click here forfile chooser

Log Manager 13-9

13

From the Print window, you can:

• Select the “Print to file” toggle button and either specify a filename, or clickon the button to the right of this field and select a file from the File Selectionwindow.

• Select the “Printer” toggle button and specify a printer name, or click on thedown arrow to the right of this field and choose one from the list. You canspecify a default printer by setting the $LPDEST environment variable.

• Click on the up or down arrows in the Copies field to increase or decreasethe number of copies (default is 1).

• Specify the title of the printout in the Banner Page Title field.

• Specify whether the information in the Log Manager table should be printedin text format or in table format by selecting either the Text or Table togglebuttons, respectively. This portion of the Print window will not appear inany instance where you can print only in text mode.

Click on the Print button to print the data according to your specifications.

ExitSelect File ➤ Exit to exit the Log Manager application. If you change any of theconfiguration properties, you receive a prompt that asks you if you want tosave your changes.

13.2.1.2 Object Menu

Selecting the Object menu displays the following pull-down menu options:

NewSelect Object ➤ New to create a new log object. After you select this option, theLog Object window, shown in Figure 13-4, appears.


13

Figure 13-4 Log Object Window

Perform the steps shown below to create a new log object. Other than clickingon either the OK or Apply button as the last step, the order of the steps is notsignificant.

• Enter the name of the MIS on which you are creating the log object in theMIS field. To create a log object on a remote MIS, you must first connect tothat MIS by using the MIS Manager. For more information, see the “MIS-to-MIS Communication” chapter in the Solstice Enterprise ManagerAdministration Guide.

• Enter the name of the log object in the logId field.

Log Manager 13-11

13

• Enter the maximum log size (in octets) in the maxLogSize field. An entry of0 indicates no limit to the log size. Such an entry poses the obvious dangerof overwhelming your storage space.

• Select either locked or unlocked for the administrativeState parameter. Thisparameter determines whether the log object can be written to (unlocked) ornot (locked). Most often, you leave this parameter in its default, unlockedstate. Select locked to prevent writing to the log object.

• Select either wrap or halt for the logFullAction parameter. This parameterdetermines what the Log Manager does when the log object reaches themaximum (maxLogSize) size. The wrap option means that the log objectwraps around to the beginning of the file and overwrites existing logrecords. The halt option means that no new records will be created for thislog object.

• Specify the log object’s discriminator construct in thediscriminatorConstruct field. A discriminator construct is an expression todecide which notification types will be accepted by a log object. Refer toSection 13.3, “Defining the Discriminator Construct,” for detailedinformation about creating discriminator constructs.

• Click on the Cancel button to cancel the create operation, or click on eitherthe OK or Apply button to create and store a new object.

DeleteSelect one or more objects from the main window, then select Object ➤ Deleteto remove the selected log object(s) from the MIS. Deleting a log object alsodeletes its corresponding log record. You will be prompted to confirm youraction before the log object and its corresponding log record are deleted.

Object PropertiesSelect one or more objects from the main window, then select Object ➤ ObjectProperties to modify or view the properties information about the selected logobject(s). This will bring up the Log Object window (Figure 13-4), allowing youto modify the selected log object as necessary. If multiple log objects areselected, then the Log Object window will display the properties for the firstlog object selected only.


13

Select AllSelect Object ➤ Select All to simultaneously select all log objects in the table.

Deselect AllSelect Object ➤ Deselect All to deselect all currently selected log objects in thetable.

13.2.2 View Menu

Select View ➤ Display Properties to open the View Properties window, shownin Figure 13-5. This window is used to configure the way in which log objectsare displayed in the Log Manager main window.


Log Manager 13-13

13

Display Attribute Name:This parameter determines whether the default attribute names or user-creatednames are used as column labels in the Log Manager main window table.

To create your own names:

1. Click on the User Defined Name toggle button.

2. Click on the Label Names button. This displays the Label Names window,shown in Figure 13-6.

Figure 13-6 Label Names Window

3. Enter a user-defined name for each attribute.

4. Click on either the OK or Apply button.

Hidden Attributes and Shown AttributesThe Hidden Attributes field lists the attributes that are hidden from the user,while the Shown Attributes field lists those attributes which are displayed inthe Log Manager main window table. Use the Show and Hide buttons tospecify which attributes to display in the Log Manager main window andwhich attributes to hide from the user, respectively.


13

Click on the Select All button at the bottom of either the Hidden Attributes orShown Attributes field to select all the attributes listed in the field. Similarly,click on the Deselect All button at the bottom of either the Hidden Attributesor Shown Attributes field to deselect all the attributes listed in the field

You can also select an attribute in the Shown Attributes field, then use theMove Up and Move Down buttons to change the order in which the attributesare displayed in the Log Manager main window table.

LoadClick on the Load button to load an existing file containing viewing propertyparameters. This brings up the Load Properties window, which allows you toselect a file from which to read.

SaveClick on the Save button to save the viewing properties you specified. Thisbrings up the Save Properties window, which allows you to select the path andfile name to which you want to save the parameters.

13.2.3 Tools Menu

Selecting the Tools menu displays the following pull-down menu options:

Configure ToolsSelect Tools ➤ Configure Tools to display the Configure Tools dialog window,which allows you to add other applications to the Log Manager Tools menu.

Alarm ManagerSelect Tools ➤ Alarm Manager to open the Alarm Manager application.

Log ViewerSelect Tools ➤ Log Viewer to open the Log Viewer application.

The Tools menu can also contain other tools you may have configured into theLog Manager by selecting Tools ➤ Configure Tools.

Log Manager 13-15

13

13.3 Defining the Discriminator ConstructA discriminator construct is an expression used to decide which notificationtypes will be accepted by a particular log object. The general rules for such anexpression are contained in the ASN.1 definition of a CMIS filter, in ISO 9595.1

Within a discriminator construct, a single test is called an item. Within an item,a relationship is written with the comparison operator preceding a pair of curlybraces, which enclose an operand. The following is the general form:

The term item is one of four keywords that can be used to specify the formatof a CMIS filter. These format specifiers can be item , and , or , or not .Table 13-3 defines these terms.

1. ISO/IEC 9595. Information technology – Open systems interconnection – Common managementinformation service definition. 1991.

item : <operator> : { <operand> }

Table 13-3 Format Specifier Definitions

Name Descriptions

item A single FilterItem, which is a choice of a test for equality, less than or equal, greater thanor equal, substring matching, or presence in. These filter words are described inTable 13-4.

and The logical AND of a set of CMIS filters.

or The logical OR of a set of CMIS filters.

not The negation of the sense of one CMIS filter.


13

The <operator> in the preceding example is the word in a given filter item.Table 13-4 defines the operators.

The <operand> is, in GDMO terms, an Attribute, which by definition is a name-value pair. So, we can further refine the general form as:

Using the and or format specifier, you can build nested filters. These are of theform:

As an example of a filter used as a discriminator construct, to test whether thesubject of an event notification is a test , the expression might be:

In the preceding example, objectClass (the attribute name) and test (theattribute value) combine to form a single attribute, against which an eventnotification will be tested for equality.

Table 13-4 Operator Definitions

Name Description

equality Is the item we are filtering equal to this operand?

substrings Is the string under consideration match the beginning, end, or any part of the string inthe operand? This breaks down to the operators initialstring , anystring , andfinalstring .

greaterOrEqual Is the item we are filtering greater than or equal to this operand?

lessOrEqual Is the item we are filtering less than or equal to this operand?

present Is the item we are filtering present in the operand?

item : <operator> : { <name_string>, <value_string> }

and : (or or ){item : <operator> : { <name_stringA>, <value_stringA> },item : <operator> : { <name_stringB>, <value_stringB> }}

item : equality : {objectClass, test }

Log Manager 13-17

13

Use the format specifier and , defined in Table 13-3, to perform a logical ANDon two filter items. For example, to test whether the subject of notification is atest and the severity of the notification is minor, specify the following:

Multiple items are separated by a comma (last character in first line above).

13.3.1 Discriminator that Accepts Notificationsof a Specific Type

The following example tests the notification type in an incoming eventnotification. The OID { 2 9 3 2 7 14 } specifies an event notification. Thenotification type is identified by the OID { 2 9 3 2 10 <x> }:

In this expression, substitute one of the values 1 through 15 for <x> from thelist of notification types shown in Table 13-5.

and : { item : equality : {objectClass, test }, item : equality : {perceivedSeverity, minor }}

item : equality : { globalForm : {2 9 3 2 7 14 }, { 2 9 3 2 10 x}}

Table 13-5 Notification Types and Numbers

Number Notification type

1 attributeValueChange

2 communicationsAlarm

3 environmentalAlarm

4 equipmentAlarm

5 integrityViolation

6 objectCreation

7 objectDeletion

8 operationalViolation

9 physicalViolation

10 processingErrorAlarm

11 qualityofServiceAlarm


13

Note – Within a discriminator construct, you can express OIDs in text, ratherthan numeric, form.

In addition to the OSI-standard notifications shown in Table 13-5, the alarmLogobject accepts alarms of type nerveCenterAlarm, the OID for which is:1.3.6.1.4.1.42.2.2.2.8.3.111.

13.3.2 Discriminator Construct with Multiple ANDs

Code Example 13-1 is a sample discriminator construct that uses the and formatspecifier to combine three filter items.

Code Example 13-1 Sample Discriminator Construct

12 relationshipChange

13 securityServiceOrMechanismViolation

14 stateChange

15 timeDomainViolation

and :{ item : equality : { attributeId globalForm : "Rec. X.721 | ISO/IEC 10165-2 : 1992":managedObjectClass, attributeValue globalForm : "Rec. X.721 | ISO/IEC 10165-2 : 1992":log },

item : equality : { attributeId globalForm : "Rec. X.721 | ISO/IEC 10165-2 : 1992":managedObjectInstance, attributeValue distinguishedName : { { attributeId "Rec. X.721 | ISO/IEC 10165-2 : 1992":systemId, attributeValue name : "minerva" } },

Table 13-5 Notification Types and Numbers

Number Notification type

Log Manager 13-19

13

The effect of the preceding construct is as follows: If there is an event of thetype attributeValueChange to the system minerva , log that event.

Note – In the above example, it is not necessary to include document names.You could type {managedObjectClass, log} instead of first discriminator.

13.3.3 A Discriminator Construct that AcceptsAll Notifications

The following exploits the fact that and over an empty set is the identityelement for and , namely 1. This produces a discriminator construct thataccepts all notifications:

This example should never be used in actual practice, because you will likelyoverwhelm your machine resources in logging data.

13.3.4 A Discriminator that Accepts No Notifications

The corresponding identity element for or yields a discriminator construct thataccepts nothing:

As with the and example, this construct is shown for tutorial purposes only,and is not intended for use in actual practice.

}, item : equality : { attributeId globalForm : "Rec. X.721 | ISO/IEC 10165-2 : 1992":eventType, attributeValue globalForm : "Rec. X.721 | ISO/IEC 10165-2 : 1992":attributeValueChange }}

and : { }

or : { }


13

13.4 Sample Discriminator ConstructsThe following subsections present the discriminator constructs you can enter inthe Log Manager’s Log Creation to create log objects that collect log records forgiven event notifications.

To complete the creation of a log object, in addition to the discriminatorconstruct, you must fill in values for maxLogSize, logFullAction,administrativeState, and operationalState. The choices of these values dependon your specific needs. The value for maxLogSize depends on your loggingrequirements and your storage resources.

13.4.1 Creation of an Object Instance

To create a log object that logs the creation of object instances, use thefollowing discriminator construct:

13.4.2 Deletion of An Object Instance

To create a log object that logs the deletion of object instances, use thefollowing discriminator construct:

item : equality: { eventType, objectCreation }

item : equality: { eventType, objectDeletion }

Log Manager 13-21

13

13.4.3 Attribute Value Change of an Object Instance

To create a log object that logs attribute value changes of object instances, usethe following discriminator construct:

item : equality: { attributeId globalForm : ”Rec. X.721 | ISO/IEC 10165-2 : 1992” : eventType, attributeValue globalForm : ”Rec. X.721 | ISO/IEC 10165-2 : 1992” : attributeValueChange }


13

13.4.4 State Changes Received From Agent

To create a log object that logs the state changes received from agents, use thefollowing discriminator construct:

13.4.5 Default Discriminator

The following is the discriminator construct shipped with EM, presented herefor tutorial purposes.

and: { not: { item : equality: { eventType, objectCreation } }, not: { item : equality: { eventType, objectDeletion } }, not: { item : equality: { eventType, attributeValueChange } } }

Log Manager 13-23

13

The default construct uses the not operator to group a set of event types. Theeffect of this construct is that if a notification is not one of the specified eventtypes, a log record is appended to alarmLog..

13.5 Log Manager Configuration FileUpon starting, the Log Manager looks for the.em_logmgr.cf configurationfile in your home directory; otherwise, it looks for it in the $EM_HOME/configdirectory. (The file names are the same in the config directory except for theabsence of the initial dot.) If the configuration file is not found, the LogManager uses the default properties.

The alphanumeric characters in each line of the configuration file must begin atthe left edge. Each statement must be on a separate line.

not : or : { item : equality : { attributeId globalForm : "Rec. X.721 | ISO/IEC 10165-2 : 1992":eventType, attributeValue globalForm : "Rec. X.721 | ISO/IEC 10165-2 : 1992":attributeValueChange }, item : equality : { attributeId globalForm : "Rec. X.721 | ISO/IEC 10165-2 : 1992":eventType, attributeValue globalForm : "EM MPA":snmAlarmEvent }, item : equality : { attributeId globalForm : "Rec. X.721 | ISO/IEC 10165-2 : 1992":eventType, attributeValue globalForm : "Rec. X.721 | ISO/IEC 10165-2 : 1992":objectCreation }, item : equality : { attributeId globalForm : "Rec. X.721 | ISO/IEC 10165-2 : 1992":eventType, attributeValue globalForm : "Rec. X.721 | ISO/IEC 10165-2 : 1992":objectDeletion }, item : equality : { attributeId globalForm : "Rec. X.721 | ISO/IEC 10165-2 : 1992":eventType, attributeValue globalForm : "Rec. X.721 | ISO/IEC 10165-2 : 1992":stateChange }}


13

The configuration file has the following format:

Table 13-6 Sample Log Manager Configuration File

display_name=nickname

label_name=default_name

show_doc_names=show

show_oids=oid

attr_name=logId

logId.name=Log Name

logId.position=1

logId.displayed=true

logId.sort_pos=-1

logId.width=10

attr_name=numberOfRecords

numberOfRecords.name=Records

numberOfRecords.position=2

numberOfRecords.displayed=true

numberOfRecords.sort_pos=-1

numberOfRecords.width=10

attr_name=administrativeState

administrativeState.name=Admin State

administrativeState.position=3

administrativeState.displayed=true

administrativeState.sort_pos=-1

administrativeState.width=12

attr_name=currentLogSize

currentLogSize.name=Current Size

currentLogSize.position=4

currentLogSize.displayed=true

currentLogSize.sort_pos=-1

Log Manager 13-25

13

The information in this file corresponds to the Properties and View Propertieswindows. Although this file shouldn’t be modified manually, you might wantto change the width field, which determines the width of the cells in the table.

currentLogSize.width=9

attr_name=maxLogSize

maxLogSize.name=Max Size

maxLogSize.position=5

maxLogSize.displayed=true

maxLogSize.sort_pos=-1

maxLogSize.width=9

attr_name=logFullAction

logFullAction.name=Full Action

logFullAction.position=6

logFullAction.displayed=true

logFullAction.sort_pos=-1

logFullAction.width=8

attr_name=discriminatorConstruct

discriminatorConstruct.name=Discriminator

discriminatorConstruct.position=7

discriminatorConstruct.displayed=true

discriminatorConstruct.sort_pos=-1

discriminatorConstruct.width=75

Table 13-6 Sample Log Manager Configuration File


13

14-1

Log Viewer 14

14.1 OverviewThe Log Viewer enables you to browse the contents of a log or log object, andview the details of a log record. Log records give you detailed information onevents that have occurred on your network. Log objects store log records, andare an important network management tool, particularly in the areas ofconfiguration, alarm, and security management. For information on managinglog objects see, Chapter 13, “Log Manager.”

14.2 Starting the Log ViewerYou can start the Log Viewer by:

• Selecting the Log Viewer icon in the Application Launcher window

• Selecting Tools ➤ Log Viewer from the Tools menu in other EM applications(for example, the Viewer or Log Manager)

Overview page 14-1

Starting the Log Viewer page 14-1

The Log Viewer Main Window page 14-3

Using the Log Viewer page 14-11

Log Viewer Configuration File page 14-21


14

• Entering the em_logview command from the command line

Note – Before invoking the Log Viewer from the command line, be sure thatthe $XFILESEARCHPATH environment variable is set. If you installed SolsticeEM in the default location, it should point to/opt/SUNWconn/em/config/%N . If this environment variable is not set, thefonts, colors, and backgrounds may not be displayed correctly.:

If you start the Log Viewer from the command line, and you are a non-rootuser, you might receive a Login window, depending upon whether or notpassword authentication is turned on. To proceed, enter your password andclick OK. Your access to the Log Viewer functions depends on the permissionsgranted to you through Access Control. For more information about passwordauthentication and granting permissions, see Chapter 9, “Access Manager.”

The optional parameters of the em_logview command are described below:

When started, the Log Viewer looks for the.em_logview.cf configuration filein your home directory. If this file is not found, the default Log Viewerproperties are used. The format of the configuration file is discussed inSection 14.5, “Log Viewer Configuration File.”

hostname% em_logview [options] &

Option Description

-help Print list of options (with descriptions) for theem_logview command.

-host < hostname> Specify the <hostname> of a remote MIS. You can specifyan IP address as the <hostname>.


-logobj < fdn> Display the log records of the specified log objects in themain window summary table.

-logrec < fdn> Displays the log in which the log record appears (same as-logobj ) and, in addition, displays the log recordspecified as fdn as the selected log record.

Log Viewer 14-3

14

14.3 The Log Viewer Main WindowWhen you open the Log Viewer main window, all of the log records for theselected log objects are displayed. The data can include any or all of thefollowing attributes:

• logRecordId

• eventTime

• eventType

• managedObjectClass

• managedObjectInstance

Log records with the most recent activity are displayed first, followed by olderrecords.

Figure 14-1 Log Viewer Main Window


14

In addition to the summary data displayed in the main window, a status barappears at the bottom. This status bar has two sections—the right side showsthe total number of records being displayed; the left side contains generalstatus information, for example, “New record received”

You can use the mouse to adjust the size of the rows or columns in the table.Place the cursor on the line in a row or column where you want to make anadjustment; the cursor changes to an arrow. Hold down the left mouse buttonand drag the cursor until the row or column is the size you want.

14.3.1 Record Details Button

This Record Details toggle button on the Log Viewer main window opens andcloses a detailed log record window, as shown in Figure 14-2. The RecordDetails window shows all the available information about the last selected logrecord.

Log Viewer 14-5

14

Figure 14-2 Record Details Window

After you have opened the Record Details window, you can click on the sashand drag it up or down to resize both the Log Viewer main window and theRecord Details window.

Additionally, you can click on the Print button to invoke the Print window,from which you can print a copy of the log record details. For mor informationon the Print window, see Section 14.3.2, “File Menu.”

Sash


14

14.3.2 File Menu

Selecting the File menu displays the following pull-down menu options:

14.3.2.1 Log Properties

Select File ➤ Log Properties to display the Properties window, which allowsyou to select the logs to display. For more information about the Propertieswindow, see Section 14.4.2, “Choosing Which Log Records to Display.”

14.3.2.2 Print

Select File ➤ Print to display the Print window, shown in Figure 14-3.






Log Viewer 14-7

14





14.3.2.3 Exit

Select File ➤ Exit to exit the Log Viewer application. If you have changed anyof the configuration properties, you receive a prompt that asks you if you wantto save your configuration changes. The changes are saved to the Log Viewerconfiguration file .em_logview.cf .

14.3.3 Object Menu

Selecting the Object menu displays the following pull-down menu options:

14.3.3.1 Find

Select Object ➤ Find to open the Find window to search for a log record. Formore information, see Section 14.4.3, “Searching For a Log Record.”

14.3.3.2 Delete

Select Object ➤ Delete to remove the currently selected log records from theMIS.

14.3.3.3 Select All

Select Object ➤ Select All to select all the log records in the table.


14


Select Object ➤ Deselect All to deselect all the currently selected log records inthe table.

14.3.4 View Menu

Selecting the View menu displays the following pull-down menu options:

14.3.4.1 Display Properties

Select View ➤ Display Properties to display the View Properties window,shown in Figure 14-8, which is used to specify the way log records aredisplayed in the Log Viewer main window. For more information on using thiswindow, see Section 14.4.5, “Modifying the Log Record Views.”

14.3.4.2 Filter Properties

Select View ➤ Filter Properties to display the Log Filter window, shown inFigure 14-4, which enables you to configure a filter that determines whichsubset of MIS alarms to display in the Alarm Manager.

Log Viewer 14-9

14

Figure 14-4 Log Filter Window

You can define up to four filters based on the following criteria:

• Object Instances

• Object classes

• Event type

• Date and time

Each Filter Select button (the buttons immediately below the word “Include”)has a pull-down menu for selecting the filter type, as shown in Figure 14-5.


14

Figure 14-5 Log Filter Pull-down Menu

Each of the four filter selection boxes allows you to select one of the twomutually exclusive alternatives. For example, if you select Only Object Classes,then you will be specifying a filter that selects only devices falling into theObject Classes that you specify. If you select All Object Classes Except, thenyou are specifying a filter that excludes alarms for devices falling into theObject Classes that you list but does not exclude alarms for devices in anyother Object Class.

If the pair in a given box in this list is grayed out, that filter has been activated.After you have defined a filter, the text in that panel in the pull-down menuwill be grayed out.

To change your selection for a filter, you must first deselect the existing choicefor that filter. To do this, click on the Filter Select button in the panel for thatfilter. This displays the filter list. Select the blank panel at the top of the list toturn off that particular filter.

To save your selected Filter Properties to a file of your choice, click on the Savebutton. You can then print this file by clicking the Print button. To load in anexisting Filter properties file, click on the Load button.

Log Viewer 14-11

14

14.3.5 Tools Menu

Selecting the Tools menu displays the following pull-down menu options:

14.3.5.1 Configure Tools

Select Tools ➤ Configure Tools to display the Configure Applications window,which allows you to add other applications to the Log Viewer Tools menu. Formore information about using the Configure Tools window, see Section 14.4.6,“Adding Other Tools to the Tool Menu.”

14.3.5.2 Alarm Manager

Select Tools ➤ Alarm Manager to open the Alarm Manager application.

14.3.5.3 Log Manager

Select Tools ➤ Log Manager to open the Log Manager application.

The Tools menu can also contain any other tools you have configured into theLog Viewer using the Configure Tools selection.

14.4 Using the Log ViewerThis section describes some of the operations you might want to perform usingthe Log Viewer, including:

• Viewing a detailed log record

• Choosing which log records to display

• Searching for a log record

• Deleting log records from the MIS

• Modifying the Log Record Views

• Adding other tools to the Tool menu

• Starting the Log Manager Application


14

14.4.1 Viewing a Detailed Log Record

To view detailed record information, select a record, then select the RecordDetails toggle button in the Log Viewer main window.

14.4.2 Choosing Which Log Records to Display

Select File ➤ Log Properties to open the Properties window, shown inFigure 14-6. This window allows you to choose which log records aredisplayed in the Log Viewer main window.


The MIS field identifies the MIS where the log records are located. TheAvailable Logs field displays all logs in the specified MIS. To display anyavailable log records in the Log Viewer main window, select the log from theAvailable Logs field and click on the Display button. To remove a log recordfrom the main window, select it from the Displayed Logs field and click on the

Log Viewer 14-13

14

Remove button. To select all log records in either the Available Logs orDisplayed Logs field, click on the Select All button beneath the appropriatefield. Conversely, you can click on the Deselect All button to deselect allcurrently selected log records in the corresponding field.

Click on either the OK or Apply buttons when you are finished.

Note – The Remove button does not remove the log from the MIS; it onlyremoves the log from the Log Viewer main window display.

14.4.3 Searching For a Log Record

All log records may not fit on the screen. You can use the scroll bar to move thedisplay up or down. This, however, can be time consuming. To quickly searchfor a specific log record(s), select Object ➤ Find to open the Find window,shown in Figure 14-7.

Figure 14-7 Find Window

To search forward for a record, enter the search criteria in the Find Text fieldand click on the Find button. The first log record with the criteria you specifyis displayed at the top of the Log Viewer main window table.

To go to the next log that meets the search criteria parameters, click again onthe Find button. Continue clicking on the Find button to go to each log recordin your search. To go back to previous logs displayed in the search, click on thePrevious button.

Note – Searching is based only on information currently in the table.


14

14.4.4 Deleting a Log Record From the MIS

To delete a log record from the MIS, select it from the Log Viewer mainwindow table and select Object ➤ Delete. You will be prompted to confirm thisaction before the log records are deleted.

Warning – After you delete a log record from the MIS you cannot retrieve it, sobe very sure that you want to do it.

14.4.5 Modifying the Log Record Views

Select View ➤ Display Properties to open the View Properties window, shownin Figure 14-8.

Log Viewer 14-15

14


The View Properties window is divided into two main sections: View andRecord Details. These sections of the View Properties window are describedbelow:


14

14.4.5.1 View

The Log Viewer main window table displays a summary of log records. Usingthe View portion of the View Properties window, you can:

• Hide or Show log records in the table, and determine the order in whichthey appear

• Select the log record attributes by which to sort

• Create your own names for the log record attributes

• Display log records using FDN or nicknames

Showing and Hiding AttributesThe Hidden Attributes field lists the attributes that are hidden from the user,while the Shown Attributes field lists those attributes which are displayed inthe Log Viewer main window table. Use the Show and Hide buttons to specifywhich attributes to display in the Log Viewer main window and whichattributes to hide from the user, respectively.

Click on the Select All button at the bottom of either the Hidden Attributes orShown Attributes field to select all the attributes listed in the field. Similarly,click on the Deselect All button at the bottom of either the Hidden Attributesor Shown Attributes field to deselect all the attributes listed in the field

You can also select an attribute in the Shown Attributes field, then use theMove Up and Move Down buttons to change the order in which the attributesare displayed in the Log Manager main window table.

Log Viewer 14-17

14

Sort OrderClick on the Sort Order button open the Sort Order window, shown inFigure 14-9, which allows you to choose the log record attributes by which youwish to sort.

Figure 14-9 Sort Order Window

To move an attribute to the Sort Order field, select that attribute in the AllAttributes field, then click on the Add button. To determine the order of thesorting criteria (which attribute is sorted on first, then second, and so on),


14

select the attribute in the Sort Order field, then click on either the Move Up orMove Down button. To remove an attribute from the Sort Order field, selectthat attribute, then click on the Remove button. To select all attributes in eitherthe All Attributes or Sort Order field, click on the Select All button at thebottom of each field. Conversely, click on the Deselect All button to deselect allcurrently selected attributes in the corresponding field.

Creating Your Own Attribute NamesYou do not have to use the default attribute names provided with yoursoftware. To create your own names, perform the following steps from theView Properties window:

1. Click on the User Defined Name toggle button in the Display AttributeName field.

2. Click on the Label Names button. This displays the Label Names window.

3. Enter a user-defined name (right column) for each attribute (left column).

4. Click on either the OK or Apply button.

Choosing the FDN or a NicknameThe default device name used in the log records is the Fully DistinguishedName (FDN). However, FDNs are often long and incomprehensible. If anickname has been created (using the em_nnconfig utility), then you canchoose to display it instead of the FDN. Click on the Nickname toggle buttonin the Display Name As field to display the nicknames.

14.4.5.2 Record Details

The Record Details portion of the View Propertied window allows you to:

• Choose to display an attribute’s full document name or its attribute name

• Choose to use a record’s textual name or OID

Log Viewer 14-19

14

14.4.5.3 Saving Your Changes

After you have set the viewing properties, you can save the parameters in a filefor future instances of the Log Viewer. To do so, click on the Save button. Thisbrings up the Select File window, which allows you to select a file from whichto read.

14.4.5.4 Loading a View Properties File

To use the view properties stored in a file from a previous instance of the LogViewer, click on the Load button. This brings up the Select File window, whichallows you to select the path and file name to which you want to save theparameters.

14.4.6 Adding Other Tools to the Tool Menu

Several other Solstice EM applications can be started directly from the LogViewer Tools menu (for example, Alarm Manager and Log Manager). You canadd other Solstice EM applications to the Tools menu, or modify or deletethose already in the menu.

Select Tools ➤ Configure Tools to open the Configure Applications window,shown in Figure 14-10. This window lists Log Manager and Alarm Manager bydefault.


14


To add an application, type in the application information and click on theAdd button.

To modify information on an application already listed in the Log Viewer Toolsmenu (for example, if the executable path for an application has changed),select the application from the Applications list. Go to the ApplicationInformation field that you are modifying and enter the new information, thenclick on the Change button.

Log Viewer 14-21

14

To delete an application from the Tools menu, select the application from thelist, then click on the Delete button. This removes the application from theTools menu; it does not remove the application from your network.

14.4.7 Starting the Log Manager from the Log Viewer

The Log Viewer allows you to browse the contents of log objects, but it is theLog Manager application that allows you to create, modify, and delete logobjects. Log objects have discriminators that determine whether a log record iscreated when an event occurs.

To open the Log Manager application, select Tools ➤ Log Manager from theLog Viewer main window.

14.5 Log Viewer Configuration FileUpon starting, the Log Viewer looks for the.em_logview.cf configurationfile in your home directory; otherwise, it looks for it in the $EM_HOME/configdirectory. (The file names are the same in the config directory except for theabsence of the initial dot.) If the configuration file is not found, the Log vieweruses the default properties.

The alphanumeric characters in each line of the configuration file must begin atthe left edge. Each statement must be on a separate line.

The configuration file has the following format:

Table 14-1 Sample Log Viewer Configuration File

display_name=fdn

label_name=default_name

show_doc_names=show

show_oids=oid

attr_name=logRecordId

logRecordId.name=Record #

logRecordId.position=1

logRecordId.displayed=true

logRecordId.width=7


14

The information in this file corresponds to the View Properties and LogProperties windows. Although this file shouldn’t be modified manually, youmight want to change the width field, which determines the width of the cellsin the table. The width denotes the number of characters in the column.

attr_name=eventTime

eventTime.name=Event Time

eventTime.position=2

eventTime.displayed=true

eventTime.width=11

attr_name=eventType

eventType.name=Event Type

eventType.position=3

eventType.displayed=true

eventType.width=14

attr_name=managedObjectClass

managedObjectClass.name=Class

managedObjectClass.position=4

managedObjectClass.displayed=true

managedObjectClass.width=12

attr_name=managedObjectInstance

managedObjectInstance.name=Instance

managedObjectInstance.position=5

managedObjectInstance.displayed=true

managedObjectInstance.width=45

Table 14-1 Sample Log Viewer Configuration File

15-1

Alarm Manager 15

15.1 OverviewThe Alarm Manager provides information concerning alarms received by theManagement Information Server (MIS). An alarm is an event or trap that hasbeen registered (by a request) in the MIS.

15.2 Starting the Alarm ManagerYou can start the Alarm Manager in any of the following ways:

• By selecting the Alarm Manager icon in the Application Launcher window• By selecting Tools ➤ Alarm Manager from the Viewer application

Overview page 15-1

Starting the Alarm Manager page 15-1

Using the Alarm Manager page 15-3

Alarm Manager Menu Bar page 15-11

Alarm States page 15-30

Alarm Associations page 15-31

Alarm Manager Default Properties page 15-32

Alarm Manager Configuration Files page 15-33


15

• By selecting Alarm Manager from the device icon pull-down menu in theViewer canvas. The device icon pull-down menu appears when you pressthe Menu mouse key over an element in the Viewer main canvas. Thismethod of starting the Alarm Manager automatically filters alarms so thatonly the alarms for the selected device are displayed.

• By entering the em_alarmmgr command from the command line:

Note – Before invoking the Alarm Manager from the command line, be surethat the $XFILESEARCHPATH environment variable is set. If you installedSolstice EM in the default location, it should point to/opt/SUNWconn/em/config/%N . If this environment variable is not set, thefonts, colors, and backgrounds may not be displayed correctly.

If you start the Alarm Manager from the command line, and you are a non-rootuser, you might receive a Login window, depending upon whether or notpassword authentication is turned on. To proceed, enter your password andclick OK. Your access to the Alarm Manager functions depends on thepermissions granted to you through Access Control. For more informationabout password authentication and granting permissions, see Chapter 9,“Access Manager.”

The optional parameters for the em_alarmmgr command are described below:

hostname% em_alarmmgr [options] &

Option Description

-help Print list of options (with descriptions) for theem_alarmmgr command.

-host < hostname> Specify the <hostname> of a remote MIS. You canspecify an IP address as the <hostname>.

-device Specify the device name.

-refresh < refresh_rate> Specify the screen refresh rate in milliseconds.

-log < log_name> Specify the log name as MIS_name:Log_name .

-file < config_file> Specify the filter configuration file.

Alarm Manager 15-3

15

15.3 Using the Alarm ManagerBy default, the Summary window (Figure 15-1) appears when the AlarmManager is invoked. This window provides a summary of alarm groups in atable format. You can choose to have alarms summarized either by alarmseverity or by the managed object instance (device) responsible for generatingthe alarm. The summary window also includes a count of duplicate alarms,which are alarms that match exactly except for EventTime, loggingTime, andlogRecordId.

Figure 15-1 Alarm Manager Summary Window

The column to the left of the Severity (or Instance) column contains the colormapping for that particular alarm severity (or instance). You can change thecolor mapping by using the Severities window in the Request Designer byselecting Edit ➤ Severities from the menu bar. For more information aboutchanging the color mapping, see the “Request Designer” chapter in the SolsticeEnterprise Manager Administration Guide. The default color mapping is shown inTable 15-1.


15

Table 15-1 Default Alarm Severity Color Mapping

As is the case with any application window appearing in a table format in theAlarm Manager, you can use the mouse to adjust the size of the cells, rows, andcolumns. You can also use the mouse to select any number of rows. Clickingonce on a row selects/deselects that row.

15.3.1 Alarm Associations Window

The Alarm Manager groups alarms that match on certain attributes, such asobject instance and event type, into alarm “associations” (see Section 15.6,“Alarm Associations”). The groups listed in the Summary window are groupsof associations. To view a particular group of alarm associations, you must firstturn alarm associations on in the Association Properties window (Figure 15-2).Select View ➤ Association Properties from the Summary window menu bar tosee this window.

Severity Color

Normal White

Indeterminate Blue

Warning Yellow

Minor Cyan

Major Orange

Critical Red

Alarm Manager 15-5

15

Figure 15-2 Association Properties Window

By default, Alarm Associations is turned off. Click on the On toggle to turnAlarm Associations on, then click on the OK button.

Notice now that the Instances button at the bottom of the Summary windowhas changed to Alarm Associations. Now, select the association group that youwant to view by positioning the mouse cursor over the row, click once whenthe cursor changes to a plus sign, then click on the Alarm Associations button.This invokes the Alarm Associations window, as shown in Figure 15-3.


15

Figure 15-3 Alarm Associations Window

15.3.2 Alarm Instances Window

Select an association in the Alarm Associations window, position the mousecursor over the appropriate row, click once when the cursor changes to a plussign, then click on the Instances button at the bottom of the AlarmAssociations window. This invokes the Alarm Instances window, shown inFigure 15-4.

Alarm Manager 15-7

15

Figure 15-4 Alarm Manager Instances Window

Both the Alarm Associations window and the Alarm Instances windowprovide you with the following information:

• Severity (for example, critical)

• Event Type (for example, nerveCenterAlarm)

• Device

• Date (timestamp)

• Ack or Clear (the alarm state—acknowledged or cleared)

• Event Details

• Ack operator (user who ack’d the alarm)

• Ack date (timestamp of the acknowledgment)

• Clear operator

Note – The Acknowledge and Clear state fields for each alarm instance in theAlarm Instances window are read-only if you have Alarm Associations turnedon (the default). Alarm states can only be changed for an entire association ifalarms are grouped into associations.


15

15.3.3 Alarm Details Window

Select either an association from the Alarm Associations window or aninstance from the Alarm Instances window, then click on the Alarm Detailsbutton at the bottom of either window. This invokes the Alarm Detailswindow, shown in Figure 15-5.

Figure 15-5 Alarm Details Window

This window displays detailed information about the selected individualalarms.

Alarm Manager 15-9

15

15.3.4 Configuring Alarm Manager

By default, the Alarm Manager main window is the Summary window. Thiscan be changed by altering the Summary field of the View Properties window,shown in Figure 15-6.



15

By selecting Off in the Summary field of the View Properties window(Figure 15-6), you can specify whether the Alarm Instances window or theAlarm Associations window is the Alarm Manager main window.

If Off is selected in the Summary field of the View Properties window, and:

• Alarm Associations is Off, the Alarm Instances window is the AlarmManager main window. All individual alarms are listed in the mainwindow.

• Alarm Associations is On, the Alarm Associations window is the mainwindow, and the various alarm associations are listed.

Likewise, you can invoke the Alarm Instances window in more than one way:

• If you have both Summary and Alarm Associations turned on, select theInstances button at the bottom of the Alarm Associations window.

• If you have either Summary or Alarm Associations turned off, select theInstances button at the bottom of the Alarm Manager main window.

• If you have both Summary and Alarm Associations turned off, the AlarmInstances window becomes the Alarm Manager main window.

Depending on how you have customized the Alarm Manager, the Summarywindow, the Alarm Associations window, or the Alarm Instances window canbe the top window in the hierarchy of windows. That is, one of these becomesthe window that is displayed when you first invoke the Alarm Manager. Thatwindow is called the main window.

15.3.5 Alarm States

One or both of the following two states can be attached to an alarm:

• Acknowledged• Cleared

Alarms that are neither acknowledged nor cleared are said to be open. TheAlarm Manager Summary window provides a summary of alarms by state.Section 15.5, “Alarm States,” provides instructions for changing alarm states.

Alarm Manager 15-11

15

By default, the Alarm Manager displays a summary of all alarms known to theMIS. The Alarm Manager can be configured to display a subset of all alarmsthrough its Alarm Filter window, enabling you to specify the types of alarmsyou want to view using GUI controls. You can filter alarms on the basis of thefollowing criteria:

• Alarm state

• Event type

• Alarm severity

• Managed object instance

• Managed object class

• Date and time

The alarms filtering information can be saved to an Alarm Manager filterproperties configuration file. Refer to Section 15.4.4.1, “Filter Properties,” fordetailed information about specifying and saving alarm filtering criteria.

See Chapter 5, “Log Management,” for a discussion of the alarm object typessupported by Solstice EM. This same chapter also describes the alarm loggingprocess.

15.4 Alarm Manager Menu BarThe Alarm Manager menu bar is displayed in each of the following windows:

• Summary window

• Alarm Associations window

• Alarm Instances window

The Tools menu is accessible only from the Alarm Manager main window.

15.4.1 File Menu

Selecting the File menu displays the pull-down menu options described below.


15

15.4.1.1 Properties

Select File ➤ Properties to display the Properties window (Figure 15-7), whichallows you to select the alarm log files you want to display from both the localMIS and remote MISs.


To purge alarms on manual clear, click on the toggle button next to Purge onManual Clear. You can restrict purging based on severity level and the age ofthe alarm. To restrict purging based on severity level, click on the buttonimmediately to the right of “Alarms of severity or below:” to retrieve a pull-down menu with the following alarm severities:

• Indeterminate

Alarm Manager 15-13

15

• Critical

• Major

• Minor

• Warning

• Cleared

Any alarm(s) having the severity you select or below are purged automaticallywhen they are manually cleared.

To purge alarms based on the age of the alarm, click on either the up or downarrows next to the Days, Hours, and Minutes boxes in the “Alarms older than”field. Any alarm(s) older than the number of days, hours, and minutes youspecify are purged when they are manually cleared.

By default, an alarm that is manually cleared generates an event. If you do notwant an event generated for each manually cleared alarm, click on the togglebutton to the left of “Clear Event Required.”

Enter the name of the local MIS or a remote MIS in the MIS field to see allavailable alarm logs in the MIS. To display a log in the Alarm Manager mainwindow, select it from the Available Logs field and click on the Display button.To remove a log from the window display, select it from the Displayed Logsfield and click on the Remove button.

Note – The Remove button does not remove the log from the MIS; it onlyremoves the log from the Alarm Manager main window display.

15.4.1.2 User Log Properties

Select File ➤ User Log Properties to retrieve the Log Properties window,shown in Figure 15-8, which allows you to specify whether or not all or someof the actions performed in the Alarm Manager are logged to a database.


15

Figure 15-8 Log Properties Window

By default, the option to log the operator actions is turned off. Click on thetoggle button to turn this option on. You can then select which items you wantor do not want to log. By default, all of the actions listed in the Select Items tolog field are logged.

If you turn the logging option on, you should specify the name of a file towhich the log information will be written. By default, this file will be created inthe directory from which the Alarm Manager was started.

Click on either the OK or Apply buttons to save your changes.

Alarm Manager 15-15

15

15.4.1.3 Print

Select File ➤ Print to display the Print window, shown in Figure 15-9.











15

15.4.1.4 Exit

Select File ➤ Exit to leave the Alarm Manager application. If you have changedany of the configuration properties, a prompt appears, asking if you want tosave your configuration changes.

15.4.2 Object Menu

The Object menu provides options that allow you to change the state ofselected alarms (or alarm associations), or to remove alarms from the displayor the alarm log. This menu is inaccessible (grayed out) in the Alarm Instanceswindow if you have the Alarm Associations feature activated. If theAssociation feature is On, alarms can only be acknowledged or cleared for awhole association at once, not on an individual alarm-by-alarm basis.

15.4.2.1 Display Text

Select Object ➤ Display Text to retrieve the Display Text Tool window, shownin Figure 15-10.

Figure 15-10 Display Text Tool Window

This window allows you to enter text data and associate that data with anexisting alarm. Text field changes are:

• Done at the alarm association level if associations are turned on

• Done at the individual alarm level if associations are turned off

• Reported by the Alarm Manager to the MIS at the individual alarm level

Alarm Manager 15-17

15

By default the Display Text column is not displayed in the tables in the AlarmAssociations and Alarm Instances windows. To change this behavior, turn onHidden Attributes in the View Properties window. You can also use the Detailsoption to view this information.

15.4.2.2 Acknowledge

Select Object ➤ Acknowledge to change the acknowledged state of the selectedalarms (or alarm associations). If the alarm is not already acknowledged,selecting this option changes its state to Acknowledged.

15.4.2.3 Clear

Select Object ➤ Clear to change the cleared state of the selected alarms (oralarm associations). If the alarm is not already cleared, selecting this optionchanges its state to Cleared.

15.4.2.4 Remove From Display

Select Object ➤ Remove From Display to remove the selected alarms fromcurrent and subsequent Alarm Manager sessions. Alarms remain in the AlarmLog but are not visible within the Alarm Manager.

15.4.2.5 Purge From Log

Select Object ➤ Purge From Log to purge the selected alarms from the AlarmLog.

15.4.3 Edit Menu

Selecting the Edit menu displays the pull-down options described below.

15.4.3.1 Select All

Select Edit ➤ Select All to select all of the alarms or groups in the currentwindow.


15


Select Edit ➤ Deselect All to deselect all of the alarms or groups selected in thecurrent window.

15.4.4 View Menu

The View menu provides options for activating and configuring the AlarmAssociation feature. You can use these options to:

• Customize the way alarms are summarized in the main window

• Customize how alarms are sorted in the Alarm Associations and AlarmInstances windows

• Define the filtering criteria for selecting the alarms to be retrieved from theMIS for display in the Alarm Manager

These options are discussed below.

Alarm Manager 15-19

15

15.4.4.1 Filter Properties

Select View ➤ Filter Properties to display the Alarm Filter window, shown inFigure 15-11, which enables you to configure a filter that determines whichsubset of MIS alarms to display in the Alarm Manager.

Figure 15-11 Alarm Filter Window

You can define up to six filters based on the following criteria:

• Object Instances

• Object Classes

• Alarm States

• Alarm Severities


15

• Event Types

• Date and Time

Each filter select button (the buttons immediately below the word “Include”)has a menu for selecting the filter type, as shown in Figure 15-12.

Figure 15-12 Pulldown Filter List

Each of the six filter selection boxes allows you to select one of the twomutually exclusive alternatives. For example, if you select Only Object Classes,you are specifying a filter that selects only devices falling into the ObjectClasses that you specify. If you select All Object Classes Except, then you arespecifying a filter that excludes alarms for devices falling into the ObjectClasses that you list but does not exclude alarms for devices in any otherObject Class.

If the pair in a given box in this list is grayed out, that filter has been activated.After you have defined a filter, the text in that panel in the pull-down menu isgrayed out.

Alarm Manager 15-21

15

To change your selection for a filter, you must first deselect the existing choicefor that filter. To do this, click on the filter select button in the panel for thatfilter. This displays the filter list. Select the blank panel at the top of the list toturn off that particular filter.

To save your selected Filter Properties to a file of your choice, click on the Savebutton. You can then print this file by clicking the Print button. To load in anexisting Filter properties file, click on the Load button.

15.4.4.2 Association Properties

Select View ➤ Association Properties to display the Association Propertieswindow, shown in Figure 15-13, which allows you to specify how alarms aregrouped, and the order in which they are displayed.

Figure 15-13 Association Properties Window


15

Alarm AssociationsThis field determines how the alarms are grouped. Select On (the default) togroup individual alarms into associations using the criteria you selected in theAssociate By field. The Alarm Manager Summary window (if Summary is On)will contain a summary of the associations.

Select Off for the Summary window to display information on groups of alarminstances. Refer to Section 15.6, “Alarm Associations,” for information aboutAlarm Associations.

Get Alarm Data FromThis field determines the order in which the alarm appear. When alarmassociations are displayed in the Alarm Associations window, the displayeddata (other than State) is taken from one of the associated alarms. You canchoose to have this data taken from the alarm with the highest severity or thealarm with the most recent date.

Associate ByAlarms are grouped in associations according to whether or not they match theattributes selected here. Attributes that can be used for associating alarms are:

• Object Instance (device)

• Event Type (for example, Nerve Center alarm)

• Probable Cause (for example, adapterError)

• Specific Problem

• Additional Text

• Add’l Info Identifier

• Additional Information

LoadClick on the Load button to save your selected Association Properties to a fileof your choice for future use.

SaveClick on the Save button to load an existing Association Properties file.

Alarm Manager 15-23

15

15.4.5 View Properties

Select View ➤ Properties to display the View Properties window(Figure 15-14), which allows you to change the way alarm log records aredisplayed.

Figure 15-14 View Properties window


15

SummaryTurn Summary Off to get a list of all alarm instances or associations on theAlarm Manager main window. Turn Summary On to display only a summaryof alarms. The default is On.

Summarize ByThis field determines the way groups of alarms are summarized in the AlarmManager main window when the Summary option is On. Groups of alarms canbe listed in order of severity or by object instance.

Show Duplicate AlarmsWhen this field is On, Summary is On, and Alarm Association is Off, thesummary line includes a count of duplicate alarms.

Display Object Name asThis field determines whether the system name or the Fully DistinguishedName (FDN) is displayed for the alarm device names.

Note – Alarm Manager “FDNs” do not necessarily have the same syntax asCMIP FDNs. Alarm Manager FDNs will have the same content as CMIP FDNsbut there might be additional keywords, such as “name.”

For detailed information on FDNs, please refer to the “Configuring SNMP TrapHandling” chapter in the Solstice Enterprise Manager Administration Guide.

Apply Alarm Color toThis field determines whether only the first column of an alarm displays thealarm color or the entire row. The default is first column only.

Display Attribute NameThis field determines whether names labels in the table columns use thesystem default names or user-defined names.

Alarm Manager 15-25

15

Label NamesClick on the Label Names button to open the Label Names window, shown inFigure 15-15.

Figure 15-15 Label Names Window


15

This window enables you to define aliases for system-defined attribute names.The column on the left displays the system-defined name for each attribute,while the column on the right displays the user-defined name (if applicable)for that attribute. To redefine an attribute name, type the new name in theappropriate field in the User Defined column.

Hidden Attributes and Shown AttributesThe Hidden Attributes and Shown Attributes fields determine which alarm logattributes are displayed. You can move any attribute from one field list to theother by selecting the item and clicking on the Show or Hide button. Theselected item moves from the original list to the other list.

Column OrderThe order in which the attributes are displayed in the Shown Attributes fielddetermines the attribute order in the Alarm Manager main window. The firstattribute in this field is the first column in the table, and so on. You can changethe table column order by selecting the attribute in the Shown Attributes fieldand clicking on the Move Up or Move Down button.

Sort OrderClick on the Sort Order button to open the Sort Order window (Figure 15-16).This window determines the order—according to selected attributes—in whichalarms are sorted in the Alarm Associations and Alarm Instances windows.

Alarm Manager 15-27

15

Figure 15-16 Sort Order Window

In the Sort Order window, you can move any attribute from one field to theother by selecting the item and clicking on the Add or Remove button. Todetermine the order of the sorting criteria (which attribute is sorted first, thensecond, and so on), click on the Move Up or Move Down button.

LoadClick on the Load button to load an existing file containing viewing propertyparameters. This brings up a menu that allows you to select the file to read.

SaveClick on the Save button to save the viewing properties you created. Thisbrings up a menu allowing you to select the file name and directory in whichto save the parameters.


15

15.4.6 Tools Menu

The Alarm Manager Tools menu enables you to launch other Solstice EMapplications, such as the Log Manager. You can add other applications to theTools menu, or modify or delete those already in the menu. The Tools menuoptions are described below.

Configure ToolsSelect Tools ➤ Configure Tools to open the Configure Applications window(Figure 15-17), which lists all the applications on your network, whether theyare included in the Alarm Manager Tools menu or not.


Alarm Manager 15-29

15

To add an application, select it from the Applications list, then click on the Addbutton.

To modify information on an application that is already listed in the AlarmManager Tools menu, select the application from the Applications list, go to theApplication Information field that you are modifying and enter the newinformation, then click on the Change button.

To remove an application from the Tools menu, select the application from thelist, then click on the Delete button. This removes the application from theTools menu; it does not remove the application from your network.

GrapherSelect Tools ➤ Grapher to open the Graph window (Figure 15-18). This menu isaccessible only from the Alarm Manager main window..

Figure 15-18 Graph Window

In this window, you specify:

• Graph—a mutually exclusive choice between a summary of all alarms or ofalarms for selected devices

• Graph Type—the type of data you have selected to graph: either the numberof alarms according to their type, or the number of alarms according to theirseverity


15

• Graph Name—the name of the file to which the graphed information is tobe saved

After you have specified this information, click on the OK button to invoke theGrapher application, or the Cancel button to dismiss the Graph windowwithout invoking the Grapher. Refer to Chapter 18, “Grapher,” for detailedinstructions on configuring and using the Grapher application.

15.5 Alarm StatesYou can attach one of the following states to an alarm:

• Acknowledged (ack’d)

• Cleared

Alarms that are neither acknowledged nor cleared are said to be open. TheAlarm Manager Summary window provides a summary of alarms by state.

To change an alarm state, first select the alarm association in the AlarmAssociations window (if you have associations turned on) or select theindividual alarm in the Alarm Instances window (if you’re not using alarmassociations). You can then change the state of the selected alarm by selectingEdit ➤ Acknowledge or Edit ➤ Clear. If you have acknowledged an alarm butwant to undo that action, select acknowledge once again. (You can also undo acleared state.)

You can also acknowledge alarms in the Alarm Associations window (if theAlarm Associations feature is On) or in the Alarm Instances window (if AlarmAssociations is Off) by clicking once in the appropriate box in the Ack’d orClear column. The user ID of the person who acknowledges an alarm is listedin the Ack Opr column. The user ID of the person who clears an alarm is listedin the Clear Opr column. The timestamp of the Ack operation is displayed inthe Ack Date column.

Note – Alarm states can be changed for alarm instances in isolation only if youdeactivate the alarm associations feature.

If you have Alarm Associations On, an alarm state is attributed to theassociation in the Alarm Associations window. The state of the association isdetermined as follows:

Alarm Manager 15-31

15

• An association is in the acknowledged state if and only if all of the alarms inthe association are acknowledged.

• An association is in the cleared state if and only if all of the alarms in thatassociation are cleared.

Alarm states can be changed only for an alarm association as a whole, not foralarm instances. The state of each individual alarm is displayed in the AlarmInstances window, but these states are read only. If you change the state of analarm association in the Alarm Associations window, you are changing thestate of all the alarm instances in that association.

By default, the Alarm Manager displays a summary of all alarms known to theMIS. The Alarm Manager can be configured to display a subset of all alarmsthrough its Alarm Filter window, enabling you to specify the types of alarmsyou want to view using GUI controls. You can filter alarms on the basis of thefollowing criteria:

• Alarm state

• Event type

• Alarm severity

• Managed object instance

• Managed object class

• Date and time

The alarms filtering information can be saved to an Alarm Manager filterproperties configuration file. Refer to Section 15.4.4.1, “Filter Properties,” fordetailed information about specifying and saving alarm filtering criteria.

See Chapter 5, “Log Management,” for a discussion of the alarm object typessupported by Solstice EM. Chapter 4 also describes the alarm logging process.

15.6 Alarm AssociationsBy default, the Alarm Manager groups alarms together into “associations.”With this feature activated, the Alarm Manager Summary window provides asummary of groups of alarm associations rather than a summary of individualalarm instances.


15

When you group alarms into associations, only the information pertaining toone of the alarms in an association is presented in the Alarm Associationswindow. The Association Properties window allows you to specify whether themost recent alarm or the alarm with the highest severity is used for thispurpose. Also, when alarms are grouped into associations, you can assign astate (such as Acknowledged) to alarms only by assigning that state to theassociation as a whole.

Alarms are grouped into an association if they have the same value for selectedparameters. You can use combinations of the following parameters to groupalarms into associations:

• Object instance (device)

• Event type (for example, NerveCenter alarm)

• Probable cause (for example, adapterError)

• Specific problem

Individual alarms are in the same association if they have the same values forthe selected parameters. For example, if you select object instance as theprinciple of association, then alarms for the same device are grouped into anassociation.

One of the main advantages to grouping alarms into an association is toquickly convey the highest severity of alarm that is related to a single problemarea. By default, alarms are grouped into associations on the basis of eventtype, managed object instance, probable cause, and specific problem. You canactivate or deactivate the alarm association feature by setting the AlarmAssociations field to On or Off on the Association Properties window.

15.7 Alarm Manager Default PropertiesThis section contains the default values for the various portions of the AlarmManager application.

15.7.1 View Properties

Below are the default parameters in the View Properties window.

• Summary: On

• Summarize By: Severity

Alarm Manager 15-33

15

• Show Duplicate Alarms: Off

• Display Object Name as: System Name

• Apply Alarm Color To: First Column Only

• Display Attribute Name: User Defined Name

• Sort Order: Severity, Instance, Event Type, Date, Ack, Clear, Ack Opr, AckDate, Clear Opr, Clear Date, Cause, Problem, Object Class, Id, AdditionalInfo Id, Additional Info Data, Additional Text

15.7.2 Association Properties

Below are the default parameters in the Association Properties window.

• Alarm Associations: Off

When Alarm Associations is Off, the Get Alarm Data From and Associate Byfields are grayed out. Below are the default parameters for these fields if AlarmAssociations is turned On.

• Get Alarm Data From: Most Recent Alarm

• Associate By: Object Instance, Event Type, Probable Cause, Specific Problem

15.7.3 Filter Properties

The only active filter is Only Alarm States. The default alarm states are Open,Ack’d, and Cleared.

15.8 Alarm Manager Configuration FilesAlarm Manager includes the following configuration files:

• .em_alarmmgr_fp.cf (Filter Properties)

• .em_alarmmgr_vp.cf (View Properties)

• .em_alarmmgr_ap.cf (Association Properties)

• .em_alarmmgr_tp.cf (Tool Properties)

• .em_alarmmgr_i18n.cf (Internationalization)


15

When the Alarm Manager is started, it looks for these files in your homedirectory. Otherwise, it looks for them in the $EM_HOME/config directory.(The file names are the same in the config directory except for the absence ofthe initial dot.) If the configuration files are not found, the Alarm Manager usesthe default properties.

15.8.1 Configuration File Formats

The alphanumeric characters in each line of each file must begin at the leftedge, and each statement must begin on a separate line. If you decide tochange any of the Alarm Manager properties, it is recommended that you doso through the properties windows provided to you through the AlarmManager GUI (except for the Internationalization configuration—you mustmanually edit em_alarmmgr_I18n.cf to change these properties).

15.8.1.1 Filter Properties Configuration File

The Filter Properties configuration file (em_alarmmgr_fp.cf ) containsstatements that fall into six groups, corresponding to the six filters. In additionto the statement:

for the date filter, there are ten types of statements that can be used, as listed inTable 15-2. Each filter other than date can contain more than one statement. Forfilters other than alarm state or date, the statements for a given filter must beeither all of the inclusionary form or all of the exclusionary form.

For the alarm state filter, there must be exactly four statements, one for each ofthe following states:

• Open

• Ack (acknowledged)

• Clear

date = <date>

Alarm Manager 15-35

15

• Ackclear (both acknowledged and cleared)

Note that <device-descr>, used with the device filter, can be one of the followingforms:

• Device name (for example, mysystem)

• Fully Distinguished Name, or FDN. Refer to the note on page 15-24 aboutAlarm Manager FDNs.

• Partial device name or FDN with one or more asterisks used as a wildcard.For example, a partial FDN would be:

An example of a partial device name would be:

You can also specify a device FDN using an asterisk at the beginning of the<device-descr> or as a replacement for the Alarm Manager keyword “name.”For example:

Table 15-2 Filter Configuration File Statement Types

Filter Inclusionary Statement Exclusionary Statement

Object Instance DEVICE = < device-descr> NOTDEVICE = < device-descr>

Object Class OBJECT_CLASS = <MOC> NOTOBJECT_CLASS = <MOC>

Alarm State ALARM_STATE = <state> NOTALARM_STATE = <state>

Alarm Severity SEVERITY = < severity> NOTSEVERITY = < severity>

Event Type ALARM_TYPE = <alarm> NOTALARM_TYPE = <alarm>

Date and Time DATE = < date> N/A

systemId=name:”bigbox”/*.

big*

systemId=*”bigbox”


15

The following is an example of a Filter Properties configuration file:

15.8.1.2 Association Properties Configuration File Format

15.8.1.3 View Properties Configuration File

The following is a sample View Properties configuration file:

## em_alarmmgr filter properties#ALARM_STATE = openALARM_STATE = ackALARM_STATE = clearALARM_STATE = ackclearNOTSEVERITY = WarningNOTDEVICE = baldspotOBJECT_CLASS = HostALARM_TYPE = InternetDATE = today

Table 15-3 Sample View Properties Configuration File

summary=on

by=severity

show_duplicates=off

display_name=nickname

label_name=user_defined

row_color=first_column

attr_name=perceivedSeverity

perceivedSeverity.label_name=Severity

perceivedSeverity.position=1

perceivedSeverity.displayed=true

perceivedSeverity.width=5

attr_name=managedObjectInstance

managedObjectInstance.label_name=Instance

Alarm Manager 15-37

15

managedObjectInstance.position=2

managedObjectInstance.displayed=true

managedObjectInstance.width=7

attr_name=eventType

eventType.label_name=Event Type

eventType.position=3

eventType.displayed=true

eventType.width=10

attr_name=eventTime

eventTime.label_name=Date

eventTime.position=4

eventTime.displayed=true

eventTime.sort_pos=1

eventTime.width=10

attr_name=ackState

ackState.label_name=Ack

ackState.position=5

ackState.displayed=true

ackState.width=3

attr_name=clearState

clearState.label_name=Clear

clearState.position=6

clearState.displayed=true

clearState.width=3

attr_name=ackOperator

ackOperator.label_name=Ack Opr

ackOperator.position=7

ackOperator.displayed=true



15

ackOperator.width=5

attr_name=ackTime

ackTime.label_name=Ack Date

ackTime.position=8

ackTime.displayed=true

ackTime.width=10

attr_name=clearOperator

clearOperator.label_name=Clear Opr

clearOperator.position=9

clearOperator.displayed=true

clearOperator.width=5

attr_name=clearTime

clearTime.label_name=Clear Date

clearTime.position=10

clearTime.displayed=true

clearTime.width=10

attr_name=probableCause

probableCause.label_name=Cause

probableCause.position=11

probableCause.displayed=true

probableCause.width=7

attr_name=specificProblems

specificProblems.label_name=Problem

specificProblems.position=12

specificProblems.displayed=true

specificProblems.width=7

attr_name=managedObjectClass

managedObjectClass.label_name=Object Class


Alarm Manager 15-39

15

managedObjectClass.position=13

managedObjectClass.displayed=true

managedObjectClass.width=7

attr_name=logRecordId

logRecordId.label_name=Id

logRecordId.position=14

logRecordId.displayed=true

logRecordId.sort_pos=2

logRecordId.width=3

attr_name=additionalInformation::identifier

additionalInformation::identifier.label_name=Additional Info Id

additionalInformation::identifier.position=15

additionalInformation::identifier.displayed=true

additionalInformation::identifier.width=10

attr_name=additionalInformation::information

additionalInformation::information.label_name=Additional Info Data

additionalInformation::information.position=16

additionalInformation::information.displayed=true

additionalInformation::information.width=15

attr_name=additionalText

additionalText.label_name=Additional Text

additionalText.position=17

additionalText.displayed=true

additionalText.width=15

attr_name=additionalInformation

additionalInformation.label_name=Additional Information

additionalInformation.displayed=false

additionalInformation.width=15



15

The order of the sort statements in the file determines the order of sortingalarms. If a sort attribute is not listed in the file, it is used for sorting after theattributes that are listed. The summary statement determines whether thesummary window is used. The by statement determines whether alarms aresummarized by severity or object instance, if summary is on. Thedisplay_name statement determines whether device name or FDN is used forthe name of the object instances.

attr_name=displayText

displayText.label_name=Display Text

displayText.displayed=false

displayText.width=7

attr_name=displayState

displayState.label_name=Display

displayState.displayed=false

displayState.width=4

attr_name=displayTime

displayTime.label_name=Display Date

displayTime.displayed=false

displayTime.width=10

attr_name=displayOperator

displayOperator.label_name=Display Opr

displayOperator.displayed=false

DisplayOperator.width=5


Alarm Manager 15-41

15

15.8.1.4 Tools Properties Configuration File Format

The Tools Properties configuration file is created when you add a new tool tothe Alarm Manager by selecting Tools ➤ Configure Tools from the menu bar,and then save the properties. Below is a sample Tools Properties configurationfile.

Table 15-4 Sample Tools Properties Configuration File

Application

{

name: discover

path: /opt/SUNWconn/em/bin/em_discover

args:

}

Application

{

name: Log Manager

path: /opt/SUNWconn/em/bin/em_logmgr

args:

}

Application

{

name: Log Viewer

path: /opt/SUNWconn/em/bin/em_logview

args:

}


15

15.8.1.5 i18n (Internationalization) Properties Configuration File

The information displayed in the data table changes dynamically, and cannotbe internationalized by the operating system localization facility. Therefore, wehave provided a mechanism whereby you can explicitly define localizationaliases for certain strings that might appear in the table. The i18n(internationalization standard) Properties Configuration file contains thereplacement strings for these items.

The i18n Properties Configuration file has the following format:

Each line in the file consists of a pair of strings. For each pair, the first string isthe string to be replaced, and the second string is the user-defined replacement.To define a replacement string, edit or add the appropriate pair in this file.

"major" "medium""minor" "low""critical" "high"

16-1

SNMP Browser 16

This chapter provides instructions for using the SNMP Browser to view, get,modify, and set SNMP MIB attribute values.

16.1 OverviewThe SNMP Browser enables you to retrieve, view, modify, and set attributesand attribute values for SNMP MIBs managed by Solstice Enterprise Manager.

The SNMP Browser enables you to browse MIB definitions without actuallycommunicating with the agent.

You can also bring up several Browser Table view windows at a time, eachdisplaying one or more Agents, MIB groups, and/or attribute set(s) for one ormore MIBs. You can mix different Agents, MIB groups, and selected attributes

Overview page 16-1

Browsing MIB Information page 16-2

Security page 16-2

Starting the SNMP Browser page 16-3

Using the SNMP Browser Windows and Menus page 16-6

Summary of Basic SNMP Browser Tasks page 16-21


16

from various groups within a single table. This enables you to construct, view,and manage complex sets of attributes and their contents for numerous MIBssimultaneously.

16.2 Browsing MIB InformationThe SNMP Browser provides three information display methods:

• SNMP MIB Information — The MIB Information area of the main windowdisplays a folder icon for each MIB document. You can open a MIBdocument folder to see which MIB groups are defined for that document.Open a group folder to see which attributes are defined for that group. (See“MIB Information Section” in “Using the SNMP Browser Windows andMenus” for a complete description of this feature.)

• Default Agent Information — The Attribute table area of the main windowenables you to view MIB values for the specified agent. (See “AttributesTable” in Section 16.5, “Using the SNMP Browser Windows and Menus” forinstructions.)

• Table Views — You can view specific MIB group and attribute informationby constructing one or more new Table views. (See “New Table” underSection 16.5.1, “File Menu” for instructions.)

16.3 SecurityAccess to the SNMP Browser and specific Browser features are controlled bythe Access Manager. The features for which access is controlled are as follows:

• BrowsingYou must have Browsing permission in order to start the Browser. If you donot, the Browser will abort.

• GETYou must have GET permission in order to open a new Table window.

• SETYou must have SET permission in order to perform a Set operation.

Refer to Chapter 9, “Access Manager” in this manual for specific instructionson enabling access to these features.

SNMP Browser 16-3

16

16.4 Starting the SNMP Browser

Note – Since all communication between the SNMP Browser and Agentspasses through the MIS, it is advisable to run Discover before starting theBrowser. For instructions on using Discover, refer to Chapter 11, “Discover” inthis manual.

You can start the SNMP Browser through any of the following methods:


• from the Viewer application


The following sections provide instructions for each of these startup methods.

16.4.1 Starting the SNMP Browser from theApplication Launcher

To start the SNMP Browser from the Application Launcher, do the following:

1. Start up the Application Launcher.To start up the Application Launcher, enter the following command at theoperating system prompt:

The optional -host <hostname> parameter allows you to specify the nameof a remote machine where the MIS is running.

For specific details on using this command, see Chapter 8, “ApplicationLauncher.”

2. Start up the SNMP Browser.Click on the SNMP Browser icon in the Launcher main window to start upthe Browser.

host% em [-host < hostname>] &


16

3. Enter your user name and password (if applicable).If Access Control is enabled for your EM installation, a UserId window mayappear. Whether this window appears depends on your UserId accesspermissions. Enter your user name and password in the appropriate fieldsin the UserId window. Then either press Return or click on OK to dismissthe UserId window and gain access to the Browser. The user access rightsassigned to you by the system administrator determine which Browserfeatures are accessible to you. Buttons and menu items for restricted featuresare grayed out.

16.4.2 Starting the SNMP Browser from the Viewer

To start up the SNMP Browser from the Viewer application, do the following:

1. Start up the Viewer application.If the Viewer application is not already running, start up the Viewer. Youcan do this by either of two methods:

• By entering the following command at the operating system prompt:

• By selecting the Viewer icon in the Application Launcher window.

See Chapter 10, “Viewer” for more detailed instructions on starting the Viewerapplication.

2. Start up the SNMP Browser.You can start up the SNMP Browser from the Viewer in any of the followingways:

• Select the SNMP Browser option from the Viewer Tools menu.• Click on the SNMP Browser icon in the Viewer tool bar.• Click on an icon in a View and select the SNMP Browser option in the

pulldown menu for that icon. If you use this method, the Browser comesup with that object as the default agent, and the attribute informationdisplayed in the Attribute table.

host% em_viewer [options] &

SNMP Browser 16-5

16

3. Enter your user name and password (if applicable).If Access Control is enabled for your EM installation, a UserId window mayappear. Whether this window appears depends on your UserId accesspermissions. Enter your user name and password in the appropriate fieldsin the UserId window. Then either press Return or click on OK to dismissthe UserId window and gain access to the Browser. The user access rightsassigned to you by the system administrator determine which Browserfeatures are accessible to you. Buttons and menu items for restricted featuresare grayed out.

16.4.3 Starting the SNMP Browser from theCommand Line

You can also start up the SNMP Browser by issuing the Browser commandfrom the operating system prompt, as follows:

Where the options are as follows:

If Access Control is enabled for your EM installation, a UserId window mayappear, prompting you for your UserId and password. Whether this windowappears depends on your UserId access permissions. Enter your user nameand password in the appropriate fields in the UserId window. Then eitherpress Return or click on OK to dismiss the UserId window and gain access to

hostname% em_snmpbrowser [options] &

Option Description

-help Print list of options (with descriptions) for theem_snmpbrowser command.


-agent < agentname> Specify the default agent name. If omitted, default isthe name of the MIS host. If -id < topo_id> is alsospecified, -id < topo_id> take precedence.

-community < string> Specify the default community string. If omitted,default is “public”.

-id < topo_id> Specify the topoNodeId. If -agent < agentname> isalso specified, -id < topo_id> takes precedence.


16

the Browser. The user access rights assigned to you by the systemadministrator determine which Browser features are accessible to you. Buttonsand menu items for restricted features are grayed out.

16.5 Using the SNMP Browser Windows and MenusWhen you first invoke the SNMP Browser, the Browser main window appearsas illustrated in Figure 16-1:

Figure 16-1 SNMP Browser Main Window

SNMP Browser 16-7

16

Figure 16-2 is an example of the SNMP Browser main window as invoked fromthe Application Launcher, and with selected document and group foldersopened:

Figure 16-2 SNMP Browser Main Window Example

If, as in this example, you invoke the Browser from the Application Launcher,the host on which the MIS is running becomes the default agent. In this case,the window displays dokusan as the default agent, and shows the documentssupported by that agent (RFC1213-MIB and SUN-MIB). The example abovealso shows selected document and group folders opened, displaying theattributes for the MIB group sunSystem .


16

If you have preselected a MIB or topology node before starting the Browser, anew Table window will also appear displaying the table for that object. (Referto Section 16.5.2, “View Menu,” below for details.)

The Browser main window consists of the following elements:

Menu BarThe main window menu bar contains buttons for invoking the following:

• File

• View

• Help


These menus and their options are described in the appropriate sections below.

AgentIn this field, enter the name of the agent you want to use as the default agent.This can be either the IP hostname or an IP address. The MIB information forthe specified agent will appear in the MIB Information section of the mainwindow.

CommunityIn this field, enter the name of the access Community for the agent.

MIB Information SectionThis section of the Browser main window displays the MIB document folders.If you have selected the View➤Show All Documents option, all documents,regardless of whether the default agent supports them, are displayed. If youhave selected View➤Supported Only, only the documents supported by thedefault agent are shown. To change which documents are supported, you mustreconfigure the agent using the EM Object Configuration Tool (refer toChapter 19, “Object Configuration Tool” in this manual).

SNMP Browser 16-9

16

Each document contains a set of one or more groups. Click on the folder iconfor a document to see the groups for that document. Click on a group foldericon to see the attribute list for that group. Select a group to display theattributes and attribute contents in the Attributes table (see below). Attributeicon colors have the following meanings:

• White — Attributes shown in white are read/write attributes. You canmodify and set values for these attributes.

• Grey — Attributes shown in grey are read only attributes. The values forthese attributes can not be altered.

Attributes TableThis section of the Browser main window displays the Attributes table. Thistable displays the set of groups and/or attributes you selected in the MIBInformation section, and the current contents for each instance of an attribute.Attribute colors have the following meanings:

• White — Attributes shown in white are read/write attributes. You canmodify and set values for these attributes.

• Grey — Attributes shown in grey are read only attributes. The values forthese attributes can not be altered.

Table <Active-Table>Click on this button to see a list of existing Table windows. The Active Tableselection appears as the label for the button. There can only be one ActiveTable at a time. All Table View operations — such as adding an attribute orgroup to a table (see Add Selected To, described below) — are applied to theActive Table, only.

Add Selected ToClick on this button to add the attributes listed in the Attributes table to theselected Active Table window.

Show AttributesClick on the Show Attributes button to toggle display of the main windowAttributes table.


16

Status LineThe left side of the status line displays the string “MIBs Supported by“<agent>,” where <agent> is that specified in the Agent field (see above). Theright side of the status line displays the string “Done: <num>%” where <num>is the current percentage of data received from the current query.

16.5.1 File Menu

Select File from the main window menu bar to see a pulldown menucontaining the following options:

ExitSelect File➤Exit to terminate the SNMP Browser program and dismiss thewindow.

New TableSelect File➤New Table to bring up a new Table window as described in thenext section.

16.5.1.1 New Table Window

Select File➤New Table to bring up a new Table window as illustrated inFigure 16-3:

SNMP Browser 16-11

16

Figure 16-3 Table Window

The Table window enables you to construct a new table for displayinginformation for the selected Agents, groups, and group attributes. You canselect and mix different groups from different Agents, and different attributesfrom different groups. You can open as many new Table windows as needed,and construct whatever combinations of Agents, groups, and attributes youwant for each table. Once a table is constructed, you can perform Get, Set, andPoll functions on the contents.

Note – Only one Table view can be active at a time. The Add Selected Tofunction in the main window applies only to the Active Table. To activate aspecific Table view, click on the <Active-Table> button next to the Add SelectedTo button in the main window and select the desired table from the pulldownmenu.


16

Note – Some attributes are read/write, some are read only. Attributes whichare read/write are shown in white; read only attributes are shown in grey.

The Table window contains the following elements:

Drag and Drop iconDrag a group folder or attribute icon from main window MIB Informationsection and drop it into the Table window Drag and Drop icon. Dragging anddropping a group folder icon adds all of the attributes for that group to thetable. Dragging and dropping a single attribute icon adds only that attribute tothe table. You can thereby include different attributes from different groups inthe table. The number of table items is not restricted.

Navigation ButtonsTo rearrange table contents, select a table item, and then click on the Navigatorbuttons to move the item to the desired location. The Navigator buttons are:

• Move Left — Move the selected column(s) left.

• Move Right — Move the selected column(s) right.

• Move Up — Move the selected row(s) up.

• Move Down — Move the selected row(s) down.

File...Select File in the Table window to see a pulldown menu containing thefollowing options:

PrintSelect File➤Print to bring up the Print request window, as illustrated inFigure 16-4:

SNMP Browser 16-13

16


The Print window enables you to print a hardcopy of the selected table, or savePrint output to a postscript file. This window contains the following elements:

Print to File:Click the selection box beside this field to send postscript output to a file.Enter the desired output filename in the Print to File: field.

...Click on the “...” button to see the File Selection window as illustrated inFigure 16-5:


16

Figure 16-5 File Selection Window

The File Selection window contains the following elements:• Filter — Enter the absolute pathname you want to use as a filter. Click on

the Filter command button (see below) to display the list of files located inthe filter directory.

• Directory — This scrollable display lists the directories under the currentfilter. Double click on an item to select it and move to that directory.

• Files — This scrollable display lists the files under the current directory.Click on an item to select it.

SNMP Browser 16-15

16

• Selection — This field displays the file currently selected. You can alsoexplicitly enter the complete pathname and filename for a file and thenclick on OK to select it.

• OK — Click on OK to implement your selection and dismiss the FileSelection window.

• Filter — Click on the Filter command button (see below) to display the listof files located in the filter directory.

• Cancel — Click on Cancel to dismiss the File Selection window withoutimplementing your selection.

Printer:Click on the selection box next to the Printer: field in the Print window toprint output to the specified printer. Enter the name of the desired printer inthe Printer: field. You can also click on the down arrow icon to see a pull-down list of available printers. Select the desired printer name to enter it inthe Printer: field.

CopiesEnter the number of copies desired. Click on the up/down arrows toincrease/decrease the specified number of copies.

Banner Page Title:Enter the string to be used as the banner page title.

TextClick on Text to print the Active Table information in text format.

TableClick on Table to capture a snapshot of the Active Table and print thesnapshot.

PrintClick on the Print button to print your selection.


16

CancelClick on the Cancel button to dismiss the Print window without issuing aprint request.

CloseSelect File➤Close in the Table window to dismiss the Table window.

Selected...Select Selected... from the Table window menu bar to see a pull-down menuwith the following options:

Move LeftSelect Selected➤Move Left to move selected columns one column to the leftwithin the table.

Move RightSelect Selected➤Move Right to move selected columns one column to the rightwithin the table.

Move DownSelect Selected➤Move Down to move selected rows down one row within thetable.

Move UpSelect Selected➤Move Up to move selected rows up one row within the table.

Edit...Select Edit... from the Table window to see a pulldown menu containing thefollowing options:

Delete SelectedSelect Edit➤Delete Selected to remove the selected table entry. This does notperform a delete operation on the agent, only a modification of the Viewtable contents.

SNMP Browser 16-17

16

Delete All ColumnsSelect Edit➤Delete All Columns to remove all table columns. This removesall attribute names (column headings) and attribute assignments (columncontents) from the table display. This does not perform any modifications toagent attribute assignments, only a modification of the View table contents.

Delete All RowsSelect Edit➤Delete All Rows to remove all rows from the table.

Select AllSelect Edit➤Select All to select the entire table.

Deselect AllSelect Edit➤Deselect All to unselect the entire table.

AgentSelect Agent in the Table window to see the Agent pulldown menu containingthe following options:

Add AgentSelect Agent➤Add Agent to see the Add Agent popup window as illustratedin Figure 16-6:

Figure 16-6 Add Agent window.


16

The Add Agent window contains the following components:

New AgentEnter the name of the agent you want to add to the Active Table. The agentnames must be valid IP addresses or hostnames. If the address is not valid,an error message appears.

CommunityEnter the community name of the agent in this field.

OKSelect OK to add the agent to the Active Table and dismiss the Add Agentwindow.

ApplySelect Apply to add the agent to the Active Table without dismissing theAdd Agent window.

CloseSelect Close to dismiss the Add Agent window. If you do not select Applybefore selecting Close, no agent will be added to the table.

Add RowSelect Agent➤Add Row to add a new (empty) row to the bottom of the table.

Delete RowSelect Agent➤Delete Row to delete the selected entry from the table.

CreateFirst, select a row in the table. Then select Agent➤Add Row to graphically adda new row to the table. The new row will be empty of values. Type in theappropriate values in the column fields of the new row. Select Agent➤Createto submit a request to the agent to create the row in the SNMP table. If theagent accepts the request, the new row will be created in the appropriate agentSNMP table. Otherwise, you will see an error message saying the agent did notallow the new row to be created.

SNMP Browser 16-19

16

Command ButtonsThe Table window contains the following command buttons, located at thebottom of the window:

SetClick on the Set button to set all selected values. If no values are selected, anerror message appears.

GetClick on the Get button to retrieve and display attribute values for all itemsselected in the View Window. If you have not selected any items, all valuesfor all items are retrieved and displayed.

Poll...Click on the Poll button at the bottom of the Table window to see the PollSetup window as illustrated in Figure 16-7:

Figure 16-7 Poll Setup Window

Use this window to specify how polling should be handled. The Poll Setupwindow contains the following elements:


16

PollThis area contains the following options:

• All — Select all entries in the table for polling.• Selected Only — Poll only selected table entries.

RateUse the slider bar to indicate the polling frequency in seconds.

StartClick on the Start button to start polling the selected table entries.

StopClick on the Stop button to stop polling operations.

CloseClick on Close to dismiss the Poll Setup window.

16.5.2 View Menu

Select View in the main window menu bar to see a pulldown tear off menuwith the following options:

Show AttributesSelect View➤Show Attributes to display the main window Attributes table.

Hide AttributesSelect View➤Hide Attributes to remove the Attributes table from the mainwindow display.

Show All DocumentsSelect View➤Show All Documents to display all available documents.

SNMP Browser 16-21

16

Supported OnlySelect View➤Supported Only to display the list of all MIBs supported by thedefault agent.

16.6 Summary of Basic SNMP Browser TasksThe following sections provide a summary of basic tasks you may want toperform using the SNMP Browser.

16.6.1 Viewing Basic MIB Information in theMain Window

The MIB information for the specified agent appears in the MIB Informationsection of the main window. To view specific information:

• Click on a MIB document folder to see which groups are included for thatMIB.

• Click on a group folder to see which attributes are included for that group.

• To see attribute information for a MIB group, select the group by clickingonce on the group name. The attribute information for that group appears inthe Attributes table in the main window.

• To see the contents for a specific attribute, select the attribute. Theinformation appears in the Attributes table.

16.6.2 Selecting a New Default Agent

The Browser displays MIB Information for the default agent in the MIBInformation section and Attribute table of the Browser main window. To selecta new default agent, do the following:

1. Enter the agent name in the Agent field of the main window and pressReturn.

2. Enter the community name in the Community field of the main windowand press Return.

The new information appears in MIB Information and Attributes table areas ofthe main window.


16

16.6.3 Creating New Tables

You can create a new Table view by the following methods:

• Select File➤New Table from the main window menu bar to bring up a newTable window. The table will have no entries.

• Use the Add Selected To feature:

a. Select a group or attribute icon from the MIB Information section ofthe main window.

b. Select New Table from the Table <Active-Table> button list in the mainwindow.

c. Click on the Add Selected To button in the main window.

16.6.4 Making Selections in Tables

You can use the following methods to select items in tables:

• Click on a row or column label to select the desired row or column.

• Use the following Edit menu options:• Select All — Select all items in table.• Deselect All — Deselect all selected items.

16.6.5 Adding New Items to a Table

To add a new item or items to a (new or existing) table, you can use any of thefollowing methods:

• Select the desired items and tables from the main window:

a. Select the desired table from the Table <Active-Table> button list.

b. Select a group or attribute in the MIB Information section of the mainwindow.

c. Click on the Add Selected To button.The selected item is added to the Active Table.

SNMP Browser 16-23

16

• Use the Drag and Drop feature in the Table window.

a. Click and hold the middle mouse button on a group or attribute icon todrag the icon.

b. Drop the icon in the Drag and Drop icon in the window.

For a group icon, this adds all of the attributes for that group to the activetable. For an attribute icon, only the selected attribute is added. You can mixAgents, groups, and attributes as desired.

If a selection is not supported, then it is not added to the table.

16.6.6 Adding and Creating New Entries in a Table

To add and create a new row in a table, do the following in the Table window:

1. Select a row in the table.Select a row to be used as a prototype for creating the new row.

2. Select Agent➤Add Row from the Table window menu bar.A new empty row will be added (graphically, only) above the selected row.

3. Type in the appropriate values in the new row.The new row will be empty of values, so you must enter the appropriatevalues for each of the column fields in the row.

4. Select Agent➤Create from the Table window menu bar.

Select Agent➤Create to submit a request to the agent to create the rowcontents. If the agent accepts the request, the new row will be created in theappropriate agent SNMP table. Otherwise, you will see an error messagesaying the agent did not allow the new row to be created.


16

16.6.7 Rearranging Table Contents

To reorder rows and columns, first select the row(s) or column(s) you want tomove. Then use one of the following methods to rearrange their order:

• Use the Navigator buttons (located next to the Drag and Drop icon) to moverows up or down, or columns left or right.

• Use the Selected... button pulldown menu options:• Move left• Move right• Move down• Move up

16.6.8 Deleting Table Contents

To delete rows or columns from a Table view, do the following:

1. Select the row(s) or column(s) to be deleted.You can select an individual row or column by clicking on the row orcolumn label, respectively. Select Edit➤Select All to select all items in thetable. Select Edit➤Deselect All to deselect any selections you have made.

2. Select the appropriate delete function from the Edit menu.The Edit menu contains the following delete options:

• Delete Selected• Delete All Rows• Delete All Columns

16.6.9 Adding Agents to a Table

To add an agent to a Table view, do the following:

1. Select Agent➤Add Agent in the Table window.The New Agent window appears.

2. Enter the IP hostname or IP address of the agent in the New Agent field.

3. Enter the community name for the agent in the Community field.

4. Click on OK.

SNMP Browser 16-25

16

16.6.10 Getting MIB Attribute Data

Note – If access control is enabled for your EM installation, you must haveGET access enabled for your UserId. Refer to Chapter 9, “Access Manager” inthis manual for instructions on enabling specific application features.

To get attribute data, do the following:

1. If the attribute is not already included in a table, add it to the appropriatetable.See Section 16.6.5, “Adding New Items to a Table” for instructions.

2. Select the attribute in the table.

3. Click on the Get button in the Table window.

16.6.11 Setting MIB Attribute Data

To set or change an attribute value, do the following:

1. Click on the attribute value you want to change in the table.

2. Erase the contents of the field and enter your new values.

3. Click on the Set button to set the new values.The Browser will send a Set Attribute request to the agent. If the agentaccepts the request, the new attribute value is set. If the agent denies therequest, the original value reappears in the attribute value field.

16.6.12 Polling

To poll for specific information, do the following:

1. Activate the appropriate Table window.

2. Select the attributes for which you want to poll (if applicable). Click onthe Poll... button in the Table window.The Poll Setup window appears. The remaining steps occur in the Poll Setupwindow.


16

3. Select All or Selected Only.

4. Set the Rate.

5. Click on the Start button to start polling.

6. Click on Close to close the Poll Setup window (optional).Polling will continue until you reopen the Poll Setup window and click onthe Stop button.

To stop polling, do the following:

1. Reopen the Poll Setup window (if closed).

2. Click on the Stop button to stop polling.

17-1

Data Viewer 17

17.1 OverviewThe Data Viewer enables you to get, view, modify, and set managementinformation for CMIP and SNM managed objects.

The Data Viewer uses the Portable Management Interface (PMI) tocommunicate with the MIS via the Management Information Server. The DataViewer is thereby able to access, display, and set data for a managed object.When you use the Data Viewer to modify and set object data, the Data Viewervalidates your changes and updates the object information in the MIS.

A key feature of the Data Viewer is that you can invoke it on a per-object basis.That is, you can run multiple instances of the application in order to view thedata from multiple managed objects.

Overview page 17-1

Starting the Data Viewer page 17-2

Using the Data Viewer Windows and Menus page 17-4


17

17.2 Starting the Data ViewerYou can start the Data Viewer by any of the following means:


• from the Viewer Application

The following sections provide instructions for each of these methods.

17.2.1 Starting the Data Viewer from theCommand Line

You can start up the Data Viewer by entering the following command at theoperating system prompt:

The optional parameters for the em_dataviewer command are describedbelow:

hostname% em_dataviewer [options] &

Option Description

-help Print list of options (with descriptions) for theem_dataviewer command.

-host <hostname> Specify the <hostname> of a remote MIS.

-o <object> Specify the object you want to view.

-id <topo_id> Specify the toponode ID of the object you want toview.

Data Viewer 17-3

17

17.2.2 Starting the Data Viewer from theViewer Application

To access the Data Viewer from the Viewer application, do the following:

1. Start up the Viewer application.You can start up the Viewer application by either of two methods:

• By entering the following command at the operating system prompt (seeChapter 10, “Viewer” for specific details):

• By selecting the Viewer icon in the Application Launcher window. To startthe Application Launcher, enter the following command at the operatingsystem prompt:

For specific details on using this command, see Chapter 8, “ApplicationLauncher.”

2. Select the managed object you want to access (optional).

In the Viewer main window, select the icon for the managed object you wantthe Data Viewer to access.

3. Start up the Data Viewer.

You can start up the Data Viewer from the Viewer by the followingmethods:• Select the Data Viewer option from the Viewer Tools menu.• Click on an icon in a view and select the Data Viewer option in the pull

down menu for that icon.

After you have invoked the Data Viewer, the main window appears, asdescribed in the next section.

host% em_viewer [options] &

host% em [options] &


17

17.3 Using the Data Viewer Windows and MenusWhen you first invoke the Data Viewer, the main window appears, asillustrated in the following example (Figure 17-1):

Figure 17-1 Data Viewer Main Window

The Data Viewer main window contains the following elements:

Target Object:In this field, enter the name of the object with which to communicate. You canenter the name of a managed object in the field box, or if you selected amanaged object prior to invoking the Data Viewer, the name of that objectappears in this field.

Solstice EM 2.0: Data Viewer

Data Viewer 17-5

17

Inspect Criteria:This area of the main window contains options for defining the filter for thetype of management data. You can select one of: SNM Schema, or GDMODefinition. Once you have made your selection, the available documents ofthat type and their associated attributes are displayed in the scrollable selectionlist.

Border and SashBetween the Inspect Criteria and Data areas of the screen is a border separatingthe two areas. The small box located on the right hand end of the border is thesash. Click on the sash and, while continuing to hold down the mouse button,move the mouse up and down to adjust the respective sizes of these two areas.

DataThis displays the data returned in response to your request.

Command ButtonsAt the bottom of the Data Viewer main window are command buttons for theoperations you can perform on the selected managed objects. These are:

GetSelect the Get button to send a request to the object specified in the TargetObject field. The current attribute values appear in the Data display area ofthe main window.

SetSelect the Set button to send a request to the object specified in the TargetObject field. This action sets the current values for a group of attributes onthe object specified.

Poll...Select Poll... in the main window to see the Polling window as described inSection 17.3.1, “The Polling Window,” below. This window enables you tospecify polling frequency, and to start and stop a polling operation.


17

17.3.1 The Polling Window

Select Poll... in the main window to see the Polling window as illustrated inFigure 17-2:

Figure 17-2 Polling Window

The Polling window contains the following elements:

Polling UnitClick on the Polling Unit menu option button to see a selection list ofavailable polling interval units. Select one of: seconds, minutes, or hours.

Polling FrequencySpecify the polling frequency by sliding the slide bar to the desired value.

Start PollingSelect the Start Polling button to start polling the specified object for thedata you requested. Once you have selected the Start Polling button, thebutton is changed to Stop Polling. Select the Stop Polling button to stoppolling the specified object for data.

Data Viewer 17-7

17

CloseSelect Close to dismiss the Polling window. Any started polling operationswill continue until you reopen the window and select Stop.

CloseSelect Close in the Data Viewer main window to terminate a single instance ofthe Data Viewer and dismiss the main window.


17

18-1

Grapher 18

18.1 OverviewThe Solstice EM Grapher application provides the capability to display datagraphically. Options are provided to customize various plotting appearances.Data can be plotted in 2D or 3D domains, with different colors and withdifferent rotation angles. Graphs can be plotted as bar charts or as surface/lineplots. If you select the 2D format, multiple datasets can be plotted on acommon graph (such as a bar chart).

The Grapher provides a way to visualize data intuitively as well ascomparatively. When data is presented to the Grapher, it calculates the displayrange automatically. Through the display range, the Grapher draws user databased on the properties chosen from the Property Modifier window. If youchoose to present data in 3D, the data canvas rotates the display base to aspecified angle. The identity, color, and string associated with each data streamdisplay in the same window.

Overview page 18-1

Starting the Grapher page 18-2

Using the Grapher Windows and Menus page 18-4

Summary of Basic Grapher Tasks page 18-16


18

18.2 Starting the GrapherYou can invoke the Grapher application in either of the following ways:


• from the Alarm Manager

Each of these methods is describe below.

18.2.1 Starting the Grapher from the Command Line

To start the grapher from the command line, enter the following command:

There are no options or arguments for this command.

18.2.2 Starting the Grapher from the Alarm Manager

To invoke the Grapher from the Alarm Manager, select the Grapher optionfrom the Tools button in the Alarm Manager main window. The AlarmManager Graph window appears, as shown in Figure 18-1:

hostname% em_grapher &

Grapher 18-3

18

Figure 18-1 Alarm Manager Graph Window

Use the Alarm Manager Graph window to specify the contents of a graphbased on Alarm Manager data. This window contains the following elements:

Graph:This field contains the following options for specifying graph contents:

Alarm SummarySelect Alarm Summary to graph a summary of all alarms.

Selected DevicesSelect Selected Devices to graph only alarms registered to selected devices

Graph Type:This field contains the following options for specifying the type of graph:

Alarm Type vs. CountSelect this to graph Alarm Type vs. Alarm Count.


18

Severity vs. CountSelect this to graph Alarm Severity vs. Alarm Count.

Graph NameIn this field, enter the name of the graph.

OKClick on OK to create the specified graph and dismiss the Alarm Manager:Graph window.

ApplyClick on Apply to create the specified graph without dismissing the AlarmManager: Graph window.

CancelClick on Cancel to cancel the graph request and dismiss the window.

18.3 Using the Grapher Windows and MenusAfter entering your graph specifications in the Alarm Manager: Graphwindow, or after invoking the Grapher directly from the command line, theGrapher main window appears, as illustrated in Figure 18-2:

Grapher 18-5

18

Figure 18-2 Grapher Main Window

The Grapher main window contains the following elements:

• Menu bar buttons• File• Object• Edit• Help

• Graph selection list


These elements are described in the sections that follow.

18.3.1 Graph Selection List

The Graph Selection List area of the Grapher main window displays a tablelisting the following graph information:

• Graph Title — This is the name of the graph(s) presently loaded into theGrapher.

• Client — This is the application used to generate the graph data.


18

• Time/Date — This is the time and date at which the graph was created.

Click on a row in this table to select that graph for Grapher operations.

18.3.2 File Menu

The File pulldown menu contains options for loading or saving selected graphsor terminating the Grapher application.

Save...Select File➤Save to see the Select File window as illustrated in Figure 18-3:


Grapher 18-7

18

FilterEnter the absolute path name you want to use as a filter. Click on the Filtercommand button to display the list of files located in the filter directory.

DirectoriesThis is a scrollable list of the directories under the current filter. Double clickon an item to select it and move to that directory.

FilesThis is a scrollable list of the files under the current directory. Click on anitem to select it.


OKClick on OK to implement your selection and dismiss the File Selectionwindow.


CancelClick on Cancel to dismiss the File Selection window without implementingyour selection.

Load...Select File➤Load... to see the File Selection window as illustrated inFigure 18-3 and describe in the section entitled “Save...,” above. Use thiswindow to select a graph file to load into the Grapher.

CloseSelect File➤Close to quit the Grapher application and dismiss the Graphermain window.


18

18.3.3 Object Menu

Select Object from the main window menu bar to see the Object menucontaining the following options:

• Properties...

• Display...

These options are described in the following sections.

18.3.3.1 Properties...

Select Object➤Properties... to see the Properties window as illustrated inFigure 18-4:

Grapher 18-9

18


Use the Properties window to specify how to display graphed data.

The Graph Properties window contains the following elements:


18

GraphThe Graph area of the Properties window contains the following fields andoptions:

NameEnter the name of the graph in this field and press Return. The propertiesinformation for that graph then appears in the Properties form.

Graph inThis field specifies the graph display style. You can select one of thefollowing: 2D or 3D. The default is 3D.

Merge in 2DUse this option to display multiple datasets in a single 2D graph. Thisoption is available if you selected 2D as the graph display style. If youselected 3D, this option is grayed out.

DatasetsThis area of the window contains properties that can be changed for individualdatasets without affecting other datasets. This is useful for displaying mergedgraphs, such as bar charts, that plot multiple datasets. The Dataset area of theProperties window contains the following fields and options:

Name:Enter the name of the dataset in this field. Next to the Name: label is anoption menu button showing the name of the selected dataset. Click on thisbutton to see a selection list of the available datasets.

VisibleSelect Yes or No to specify whether to display the selected dataset. Thedefault is Yes.

Surface ColorIn this field, specify the color to use as the top surface of the selected datasetplot. Click on the menu option button to see a selection list of availablecolors. The default is Red.

Grapher 18-11

18

Bar ColorIn this field, specify the color to use for the selected dataset when displayedas a bar in a bar chart. The default is Red.

Dataset/Graph PropertiesIf the selected graph does not contain merged datasets, this area of theProperties window is labeled “Dataset Properties.” If this is a merged graphwith multiple datasets, it is labeled “Graph Properties.” The attributes in thisarea apply to all datasets in a single graph. The Dataset/Graph Properties areacontains the following fields and options:

FillIn this field, specify whether to use the Fill display style (ON/OFF). Filldisplays each graph as a solid. The default is ON.

MethodIn this field, specify the plotting method. You can select one of thefollowing: Surface (line graph), Bar (bar chart), or Overlayed (for example,overlay a surface graph on a bar chart). The default is Bar.

DynamicIn this field, specify the plotting dynamic. You can select one of thefollowing: Absolute, Cumulative, or Delta. The default is Absolute.

ColorsThis area of the Properties window contains options for specifying the colors touse for graph display. Next to each field is a menu option button which youcan click to see a selection list of available colors. The fields and options are asfollows:

EdgeSpecify the color to use for surface boundaries in the graph. The default isblack.


18

BackgroundSpecify the color to use as the graph window background. The default iswhite.

AxisSpecify the color to use for text and the edge along the axes. The default isblack.

Data AreaSpecify the color to use as the graph area background. The default is white.

Print...Select Print to see the Print window as illustrated in Figure 18-5:

Figure 18-5 Grapher Print Window

The print window enables you to print a hardcopy of the graph or save printeroutput to a file. This window contains the following elements:

Grapher 18-13

18

Send Output to FileSelect this option to send print output to a postscript file only.

Send output to PrinterSelect this option to print a hardcopy of the graph.

File Name:If you have selected the Send Output to File option, in this field enter thename of the file to which you want the output saved.

Printer Name:If you have selected Send Output to Printer, in this field enter the name ofthe printer on which to print.

PrintClick on the Print button to send your print request and dismiss the printwindow.

CancelClick on the Cancel button to close the window without issuing a printrequest.

RotationsThis area of the Properties window contains options for specifying displayrotation. Graphs can be rotated on all three (X, Y, Z) axes from 0 to 360 degreesentering a rotation value. Type in a value or click on the arrow buttons toincrease or decrease the entered value. This feature is available if you selected3D as the graph type, otherwise it is grayed out.

OKClick on OK to implement your specifications and close the Properties window.

ApplyClick on Apply to implement your choices without dismissing the Propertieswindow.


18

CancelClick on Cancel to dismiss the Properties window without implementing anymodifications to the original specifications.

18.3.3.2 Display...

Select Object➤Display... to display selected graphs. If you select multiplegraphs, there will be a separate window for each graph. Figure 18-6 is anexample of a graph displayed in 3D style:

Figure 18-6 Example of a 3D Display Style Graph

Figure 18-7 is an example of a graph displayed in 2D style:

Grapher 18-15

18

Figure 18-7 Example of a 2D Display Style Graph

The Display window contains the following command buttons:

CloseClick on Close to dismiss the Display window.

Properties...Click on Properties... to see the Properties window as described in“Section 18.3.3.1, “Properties...”


18

18.3.4 Edit Menu

Select Edit from the main window menu bar to see the Edit pulldown menu.This menu contains the following options:

Select AllSelect Edit➤Select All to select all the graphs listed in the main window.

DeleteSelect Edit➤Delete to delete the selected graphs from the graph list anddismiss the display for that graph.

18.4 Summary of Basic Grapher TasksThe following sections describe the steps involved in using Grapher functions.

18.4.1 Displaying Data Graphs

The Graph Display is the window in which the graphed data is displayed.How the data is displayed is determined by the parameters set in the GraphProperties window. The Graph Display window is capable of displayinggraphs in 2D or 3D format.When data is displayed in 3D, you can rotate thegraph to display it at different angles.

To display a data graph:

• Select the graph from the list in the Grapher main window

• Select Object➤Display.

A window displaying the selected graph appears.

18.4.2 Zooming, Scaling, and ResettingGraph Displays

The Display window provides the following display control features.

Grapher 18-17

18

• Zooming in — To zoom in on a particular area of the graph, place the mousein one corner of the area you want to expand. Hold down the Control keywhile holding down the Select mouse button. An area selection rectangleappears. Drag the mouse to select an area to enlarge, and release the mousebutton.

• Resizing — You can resize the entire graph in the Graph Display window bypressing the Adjust mouse button while holding down the Control key.

• Resetting — Press “r” to return to the original view of the graph.


18

19-1

Object Configuration Tool 19

19.1 OverviewThe Object Configuration Tool (hereafter OCT) allows you to configure andbrowse the attributes of a managed object in the Viewer. The tool is used in thefollowing situations:

• After using the Object Palette to create a managed object’s icon in theViewer, you use the OCT to assign a name and other basic attributes to thaticon.

• For a managed object that is already displayed in the Viewer, you use theOCT to change information—such as the agents supported, the device type,or SNMP community strings—about the managed object.

In the context of the Object Configuration Tool, a managed object is:

• An individual, manageable network element, such as a workstation, bridge,link, or router, residing in the Management Information Server (MIS). Thisis an element or a connection.

Overview page 19-1

Starting the Object Configuration Tool page 19-2

Using the Object Configuration Tool page 19-4


19

• An object that contains other objects, such as a subnetwork or a network.This is a container object.

The configuration for a container object that contains other objects is differentfrom the configuration of an element or connection. The OCT grays out buttonsand fields for items that are not appropriate for objects of a given category,element, connection, or container.

The attributes that are viewable/configurable through the OCT are, with fewexceptions, agent-related.

The OCT builds its windows, including windows that are dynamicallyupdated, using data obtained from the MIS. The normal flow is to have theOCT get the information from the MIS and display the current data for you tobrowse. If you modify the data and apply changes, the OCT validates thechanges and updates the object information in the MIS accordingly.

OCT can be used in the following ways:

• You can invoke the OCT on a per-object basis, meaning you can runmultiple instances of the tool at once.

• You can select multiple objects in the Viewer and configure those objects byrunning only one instance of OCT. If you select multiple elements ofdifferent types, OCT will display the properties of the first network elementlisted in the Name field. If you select multiple objects of different states (forexample, a device and a container), then nothing will appear in the ObjectDescription field of the OCT scrolling pane.

• You can run one instance of OCT and configure multiple objects that sharethe same properties.

It is not possible, however, to select one object in the viewer and createmultiple objects based on that object.

19.2 Starting the Object Configuration ToolThere are four ways to invoke the OCT from the Viewer:

• For any element’s icon in the Viewer other than a view, activate (double-click on) the icon in the Viewer’s canvas.

• For any element’s icon in the Viewer, use the third mouse button to retrievea pop-up menu, then select Object Properties from that menu.

Object Configuration Tool 19-3

19

• After selecting a managed object, click on the OCT icon on the Viewer’s toolbar. The OCT icon is the farthest icon on the left.

• After selecting a managed object, select Object ➤ Object Properties from theViewer’s menu bar.

You can also invoke OCT from the command line with the followingcommand:

Note – Before invoking OCT from the command line, be sure that the$XFILESEARCHPATH environment variable is set. If you installed Solstice EMin the default location, it should point to $EM_HOME/config/%N . If thisenvironment variable is not set, the fonts, colors, and backgrounds may not bedisplayed correctly.

If you start OCT from the command line, and you are a non-root user, youmight receive a Login window, depending upon whether or not passwordauthentication is turned on. To proceed, enter your password and click OK.Your access to OCT functions depends on the permissions granted to youthrough Access Control. For more information about password authenticationand granting permissions, see Chapter 9, “Access Manager.”

The available command line options are described below.

hostname% em_oct [options] &

Option Description

-help Print list of options (with descriptions) for the em_octcommand.


-cmip Configure a CMIP object.

-id < id>... Specify topology IDs. Multiple IDs are delimited by aspace.

-link < id1> < id2> Create a link between <id1> and <id2>.

-mis Configure an MIS object.

-name < name>... Specify the name of an object. Multiple names aredelimited by a space.


19

Note – Using the -cmip option with the em_oct command invokes the CMIPConfiguration widow. This replaces the em_cmipconfig command availablein previous releases of Solstice EM.

19.3 Using the Object Configuration ToolAfter OCT is invoked, the OCT main window (Figure 19-1) appears.

-parent < parent_id> Specify the parent of the object you want to create.

-rpc Configure an RPC object.

-snmp Configure an SNMP object.

-type < type> Specify the topology type of the object you want tocreate. Available types are Router, Bridge, Hub, Host,Server, Pc, Device, Bus, Printer, Sunws, Container,Subnetwork, Network, Universe, Link, Hexagon,Hexagon120, OmniSector, Circle.

Option Description


19

Figure 19-1 Object Configuration Tool Window

At the very top of this window is a panel containing:

ScrollingPane

PropertiesBrowser


19

• A list of topology node names. (If you select multiple topology nodes in theViewer and then invoke OCT, all of the names for those topology nodesappear in this list.)

• The Name field

• The Type field

Below this top panel, the OCT window is divided into two panes:

• A Properties Browser on the left

• A Scrolling Pane for object properties on the right

The scrolling pane is made up of “pages” of properties which are groupedunder a heading, such as “Object Description” or “Agent.”

You can open and/or close the page under a particular heading by:

• Activating (double-clicking on) that heading in the Properties Browser

• Selecting the folder next to the heading in the scrolling pane

Select (single-click) one of the headings in the Properties Browser to make thatsection visible in the scrolling pane.

19.3.1 Name Field

The Name field allows you to add and/or change the name of an object. Tochange the name of an object, type in a name and click on either the OK orApply button at the bottom of the OCT window.

To add the name of an object, enter the name in the Name field and click on theAdd button. In create mode, one object will be created for each name you enter,and you can enter as many names as you want. Every object created will sharethe properties defined in the OCT window. This feature makes it very easy tocreate multiple objects that share the same properties. However, it only appliesif the first object is a newly created object. It is not possible to create multipleobjects based on a previously existing object.

In edit mode, you can enter the name(s) of existing objects. As many names asyou want can be entered. After you click on either the OK or Apply button,every object you specify will take on the properties defined in the OCTwindow.


19

19.3.2 Type Field

The Type field allows you to change the type of an object.

Click on the button in this field to retrieve a pull-down list of the variousdevice types that you can change to. This list will vary depending on the typeof object you are configuring.

19.3.3 Object Description

The Object Description page allows you to specify general information aboutthe object, depending on the object type. Table 19-1 shows the various objecttypes and their respective configurable data:

Table 19-1 Object Types and Configurable Data

Object Type Configurable Data

Container defaultData

Subnetwork subnetData, snm-viewdotsubnetData, snm-viewdotcampusData

Network networkData, snm-viewdotbuildingData, snm-viewdotnetworkData, snm-viewdotstarData,snm-viewdotringData, snm-viewdotbusData

Universe defaultData

Device defaultData

Bus defaultData, snm-busdotethernetData

Router routerData, snm-componentdotrouterData

Bridge defaultData, snm-componentdotbridgeData

Hub defaultData, snm-componentdothubData

Host hostData, snm-componentdotss1Data, snm-componentdotss2Data, snm-componentdotss5Data,snm-componentdotipcData, snm-componentdotipxData, snm-componentdotlxData,snm-componentdotss10Data, snm-componentdotss20Data, snm-componentdotsun3Data,snm-componentdotsun4Data, snm-componentdotsun470Data, snm-componentdotgenwsData,snm-componentdotworkstationData, snm-componentdotgenhostData,snm-componentdotlaptopData, snm-componentdotxhynterminalData,snm-componentdotlanboxData

Interface defaultData


19

If you invoke OCT by selecting an existing object in the Viewer, theconfiguration values for that object will be read from the MIS and will be filledin automatically. If you are trying to configure a new object, all of theconfiguration values will be blank, and you can fill them in accordingly.

For more information on configuring the topoNodeUserData attribute for eachtopology node, see the “Topology Database Service” chapter in the SolsticeEnterprise Manager Application Development Guide.

19.3.3.1 Configuring Multiple Data Fields

Consider the configuration data for a router, shown in Figure 19-2.

Server defaultData, snm-componentdotsunhynserverData, snm-componentdotsc1000Data,snm-componentdotsc2000Data, snm-componentdotss330Data, snm-componentdotss370Data,snm-componentdotserverData, snm-componentdottermsrvrData

Pc hostData, snm-componentdotsun386Data, snm-componentdotpcData

Sunws hostData. snm-componentdotsunhynworkstationData, snm-componentdotsunhyndesksideData

Printer hostData, snm-componentdotlaserwriterData, snm-componentdotprinterData,snm-componentdotnewsprinterData

Link linkData, snm-connectiondotlinkData, snm-connectiondotrs232Data

Hexagon defaultData

Hexagon120 defaultData

OmniSector defaultData

Circle defaultData

Table 19-1 Object Types and Configurable Data

Object Type Configurable Data


19

Figure 19-2 Router Configuration Data

The configuration data fields are blank, indicating that a new router is beingconfigured.

Notice that the Add and Delete buttons are active and that each descriptionfield name has “[1]” appended to it. The fact that the Add and Delete buttonsare active means that multiple description fields may be displayed for you toconfigure by clicking on the Add button. In the case of a router, the fivedescription fields in topoRouterData allow you to configure one of the router’sinterfaces. To configure a second interface, click on the Add button. The samefive description fields will appear, only they will be appended with “[2]”,enabling you to configure the second interface.

To delete a description field, click on the Delete button. A separate windowwill be displayed (Figure 19-3). Select the description field number(s) you wantto delete, then click on either the OK (dismisses the window) or Apply button(does not dismiss the window).


19

Figure 19-3 Delete Description Field Window

If multiple configuration is not allowed, the Add and Delete buttons will begrayed out.

19.3.4 Agent

The Agent page allows you to configure the selected object for specific agents.Clicking on the button immediately below the Change button in the Agentpage gives you a pull-down menu with the following agents:

• CMIP agents

• MIS agents

• RPC agents

• SNMP agents

To change the configuration of an agent, select the agent in the table, then clickon the Change button. For example, if you select an existing SNMP agent andclick on the Change button, you will receive the SNMP Configuration window.One such configuration window exists for each type of agent. For moreinformation, see the subsection below for the appropriate agent.


19

You can add any type of agent by selecting the Add button, or select an agentfrom the table and click on the Delete button to delete an agent. You can alsoclick on the Add Default button for all agents except CMIP agents to create adefault agent. (There is no such thing as a default CMIP agent.)

19.3.4.1 Default Agents

If you select an agent other than CMIP, and click on the Add Default button,the value <default> is added to both the MO Name and MO RDN columns ofthe Agent table.

The <default> MO Name refers to the fact that the agent object in theManagement Information Tree (MIT) has the same name as the device you areconfiguring. The MO RDN refers to the relative position in the MIT where themanagement information for this device lives. The <default> MO RDN isalways the base of the agent.

19.3.4.2 CMIP Agents

If you want to configure your own CMIP agent, you must retrieve the CMIPConfiguration window, shown in Figure 19-4, by:

• Selecting CMIP from the pull-down menu, then clicking on the Add button


Note – Using the -cmip option from the command line replaces theem_cmipconfig utility, available in previous releases of Solstice EM.

hostname% em_oct -cmip &


19

Figure 19-4 CMIP Configuration Window

The various fields and parameters of the CMIP Configuration window aredescribed in the following subsections.


19

Entity NameSpecify the name of the remote MIS with which you want to communicate. Thevalue can be a string, object identifier (OID), or distinguished name (DN).Click on the down arrow to see a list of known MISs. To delete an MIS, click onthe Delete button, select an MIS from the resulting list, then click on the OKbutton.

After specifying an MIS, all the other fields in this window for whichinformation exists in the MIS will be filled in.

Agents DNsThis field displays the list of distinguished names (DN) of objects that theagent manages. When configuring a CMIP agent for a particular topologynode, you must select an Agent DN (from the list) by which that topology nodeis managed.

MO DNSpecify the DN (top-most node) of the MIT to be managed by the remote MIS.

For example, if the remote MIS is located on a machine called poignant , enter/systemId=name:”poignant” in the MO DN field and click on the Addbutton.

/systemId=name:”poignant” will appear in the Agents DNs field. Todelete a DN, select the one you want to delete and click on the Delete button.

MPA AddressesSelect the Default toggle button to apply the default values for the MPA Hostand MPA Port. The default host is <localhost>, and the default port number is5557. To customize these values, select the Custom toggle button and enter theMPA host and port number.

Presentation AddressFor MIS-MIS awareness, you must enter the appropriate Presentation Selector,Session Selector, Transport Selector, and Network SAP for the agent you areconfiguring.

Click on the Apply button to create the object, or click on the OK button tocreate the object and dismiss the CMIP Configuration window.


19

19.3.4.3 MIS Agents

Select MIS from the pull-down menu and click on the Add Default button tocreate a default MIS agent for all objects whose names appear in the Namefield window. One agent is created for each object in the Name field window,effectively creating a one-to-one relationship between the agents and the objectnames.

If you want to configure your own MIS agent, you must retrieve the MISConfiguration window, shown in Figure 19-5, by:

• Selecting MIS from the pull-down menu, then clicking on the Add button


Figure 19-5 MIS Configuration Window

Configuring an MIS agent in this manner creates a one-to-many relationshipbetween the agent and the object names.

The various fields and parameters of the MIS Configuration window aredescribed in the following subsections.

hostname% em_oct -mis &


19

MO NameIn this field, specify the name of the managed object (MO), or click on thedown arrow to choose a name from the resulting list.

MO DNSpecify the distinguished name (DN) of the managed object in this field byclicking on the Browser button, selecting the desired DN from the list, thenclicking on the Add button. You cannot manually edit this field.

Note – This field is grayed out if the MIS Configuration window was invokedfrom the command line using em_oct -mis .

PortSpecify the port number to connect to in order to communicate with the MIS.The default port number is 5555.

19.3.4.4 RPC Agents

Select RPC from the pull-down menu and click on the Add Default button tocreate a default RPC agent for all objects whose names appear in the Namefield window. One agent is created for each object in the Name field window,effectively creating a one-to-one relationship between the agents and the objectnames.

If you want to configure your own RPC agent, you must retrieve the RPCConfiguration window, shown in Figure 19-6, by:

• Select RPC from the pull-down menu, then clicking on the Add button

• Enter the following command from the command line

hostname% em_oct -rpc &


19

Figure 19-6 RPC Configuration Window

Configuring an RPC agent in this manner creates a one-to-many relationshipbetween the agent and the object names.

The various fields and parameters of the RPC Configuration window aredescribed in the following subsections.

MO NameSpecify the name of the managed object (MO) in this field. After you enter aname and press Return, the default values for the rest of the fields except forthe MO RDN field are displayed.


19

MO RDNSpecify the relative distinguished name (RDN) of the managed object in thisfield by clicking on the Browser button, selecting the desired RDN from thelist, then clicking on the Add button. You cannot manually edit this field.

Note – This field is grayed out if the RPC Configuration window was invokedfrom the command line using em_oct -rpc .

Read CommunitySpecify the read community permissions in this field. The default setting ispublic which allows general read access to the object’s management data.

Write CommunitySpecify the write community permissions in this field. The default setting isprivate , which denies general write access to the object’s management data.

AgentsThe SunNet Manager (SNM) RPC-based agents and proxy agents currentlyconfigured for the object are listed in the table in this field. The Agent Namecolumn contains the name of the non-proxy or proxy agent, while the ProxyHost column contains the name of the proxy host.

You can enter an SNM schema or proxy agent in the Agent Name column ofthe table by typing in the name in the field immediately beneath the table, orclicking on the down arrow in this field to see a pull-down menu of availableSNM schemas and proxy agents. To add the name, click on the Add button. Ifyou have added a proxy agent, you can click on the corresponding cell in theProxy Host column and change the name of the proxy host.

In the pull-down menu of available SNM schemas and proxy agents, SNMschemas take on the form RPC Agent - < agent>, while proxy agents take on theform RPC Proxy - < agent>.


19

19.3.4.5 SNMP Agents

Select SNMP from the pull-down menu and click on the Add Default button tocreate a default SNMP agent for all objects whose names appear in the Namefield window. One agent is created for each object in the Name field window,effectively creating a one-to-one relationship between the agents and the objectnames.

If you want to configure your own SNMP agent, you must retrieve the SNMPConfiguration window, shown in Figure 19-7, by:

• Selecting SNMP from the pull-down menu, then clicking on the Add button


hostname% em_oct -snmp &


19

Figure 19-7 SNMP Configuration Window

Configuring an SNMP agent in this manner creates a one-to-many relationshipbetween the agent and the object names.

The various fields and parameters of the SNMP Configuration window aredescribed in the following subsections.

MO NameSpecify the name of the managed object (MO) in this field. After you enter aname and press return, the default values for the rest of the fields except forthe MO RDN field are displayed.


19

MO RDNSpecify the relative distinguished name (RDN) of the managed object in thisfield by clicking on the Browser button, selecting the desired RDN from thelist, then clicking on the Add button. You cannot manually edit this field.

Note – This field is grayed out if the SNMP Configuration window wasinvoked from the command line using em_oct -snmp .

IP AddressSpecify the IP address of the managed object in this field.

PortSpecify the port number of the managed object in this field. The default portnumber is 161.

Read CommunitySpecify the read community permissions in this field. The default setting ispublic , which allows general read access to the object’s management data.

Write CommunitySpecify the write community permissions in this field. The default setting isprivate , which denies general write access to the object’s management data.

SNMP MIBsThe SNMP MIBs currently configured for the object are listed. To add a MIB,click on the down arrow immediately to the right of this field to see a list ofavailable SNMP MIBs, select one from the list, then click on the Add button. Todelete a MIB, select the MIB you want to delete, then click on the Deletebutton.


19

19.3.5 Display Status

The display status page allows you to activate or deactivate severitypropagation, which causes the Alarm Service to update the viewer icon colorto reflect the highest (most severe) uncleared alarm log record against thaticon. For more information, see Chapter 6, “Alarm Service.”

If the object you are configuring is any monitor object (Hexagon, Hexagon120,OmniSector, or Circle), there will be some additional parameters in addition tothe Propagate Severity field:

• Hide Members window

• Show Members window

• Rotation field

Hide Members and Show MembersBy default, the members of a monitor object appear in the Hide Memberswindow. Select an object and click on the Show button to move that member tothe Show Members window. You can arrange the order in which the membersappear in the Show Members window by clicking on the Move Up and MoveDown buttons as needed.

Click on the Apply button at the bottom of the OCT window to see the effectsof your change on the monitor object icon in the Viewer.

Rotation FieldClick and drag the button along the slide bar in the Rotation field to change theorientation of the monitor object. Moving the button to the right increases theangle of rotation, while moving it to the left decreases the angle of rotation.

You must click on the Apply button at the bottom of the OCT window to seethe effects of your change on the monitor object icon in the Viewer.

19.3.6 Coordinates

The Coordinates page allows you to set the coordinates of an object in theViewer.


19

There are two different coordinate systems for fixing the location of an object ina view: logical or geographical. These correspond to the Logical View andGeographical View settings in the View Properties window. See Chapter 10,“Viewer,” for detailed information. The coordinates of an object can be set bydragging an object with the mouse in the Viewer, or by entering coordinates inthe OCT.

20-1

Object Editor/Browser 20

20.1 OverviewThe Object/Editor (OBED) Browser allows you to view any of the objects in aSolstice EM Management Information Server’s (MIS) Management InformationTree (MIT).

The MIT contains internal objects representing all managed objects known to aparticular Solstice EM MIS. The managed objects, in turn, can representphysical devices (for example, hosts, bridges, routers), components of thosedevices, virtual objects (such as connections or queues), or transitory objectscreated by the various applications and services that communicate with theSolstice EM MIS.

Using OBED, you can:

Overview page 20-1

Starting OBED page 20-2

OBED’s Main Window page 20-4

File Menu page 20-6

Object Menu page 20-8

Object Configuration Window page 20-15

Using the Object Editor to Access the Objects in a CMIP Agent page 20-19


20

• Navigate around the Management Information Tree (MIT)

• View all or a portion of the MIT

• Inspect, modify, or delete any object in the MIT

• Create a new object from one of the class definitions in the MIS or from anexisting instance in the MIS, through inheritance

• Specify gets, sets, and actions for selected objects

• Display and edit CMIP and SNMP object attribute information

• Use CMIP filters and scoping for selecting objects, and for carrying outoperations such as gets and sets

20.2 Starting OBEDStart OBED by selecting the Object Editor icon in the Application Launcherwindow. (Refer to Chapter 8, “Application Launcher,” for detailed informationabout the Application Launcher.) You can also invoke OBED and connect it toan MIS running on a remote machine by using a command such as thefollowing:

If you start OBED from the command line, and you are a non-root user, youmight receive a Login window, depending upon whether or not passwordauthentication is turned on. To proceed, enter your password and click OK.Your access to OBED functions depends on the permissions granted to youthrough Access Control. For more information about password authenticationand granting permissions, see Chapter 9, “Access Manager.”

The optional command line parameters are described below:

-host <hostname>Use this parameter to specify the name of the machine where the remoteMIS is running.

hostname % em_obed -host < hostname> -root < root_object> -scope < num>

Object Editor/Browser 20-3

20

-root <root_object>Use this parameter to specify the object you want to be the root of the viewdisplayed in OBED. For example:

-scope <num>Use this parameter to specify how far down in the MIT hierarchy thedisplay is to reach. The default is two levels down.

Upon starting OBED, you see the window, shown in Figure 20-1:

hostname% em_obed -host npal -root ‘/systemId=name”:npal”’ -scope 1


20

Figure 20-1 OBED Main Window

20.3 OBED’s Main WindowOBED’s main window (Figure 20-1) contains three parts:

• A menu bar


20

• A text field containing the path to the currently selected object (the name ofits parent)

• An MIT Navigator that shows the object instance hierarchy (or some portionof it)

The number of objects selected is displayed in the lower right corner of themain window.

20.3.1 MIT Navigator

The MIT is a tree structure with a single root. Objects are arranged in the treeby their containment relationships; in other words, below each object are theobjects it contains.

The MIT Navigator provides a visual display of the MIT’s tree structure inindented text form, as shown in Figure 20-1.

The navigator represents the MIT hierarchy as a textual list of distinguishednames. Each level in the hierarchy is indented below the level above. A foldericon appears to the left of each row. If the folder icon is closed, click once on itto open the folder. Any subordinate objects at a lower level in the hierarchy aredisplayed when you open a folder.

Each object in the tree is identified by its path from the root. In the display, yousee the distinguished name of the current object, and a list of the objects fromwhich the current object is selected. When you launch OBED, the initial displayshows the list of the objects contained by the system object.

You can invoke the Object Configuration window to initiate a Get or Setoperation for an object by double-clicking on that object in the navigator. Youcan open as many Object Configuration windows as you want by repeatingthis procedure. The Object Configuration window is described in Section 20.6,“Object Configuration Window.”

20.3.2 Path

The Path field in the OBED main window displays the path of the currentlyselected object. When you select an object in the Navigator window, that line ishighlighted. You can select multiple objects in this way. To deselect an objectthat is currently selected, click on that object again.


20

If you have multiple objects selected, the Path field continues to show the pathof the first object you selected, but the path is grayed out. To display a newpath, you must first deselect the currently selected objects, then select a newobject.

20.4 File MenuSelecting the File menu displays the pull-down menu options described in thefollowing sections.

20.4.1 Properties...

Select File ➤ Properties to open the Properties window (Figure 20-2), whichallows you to set your default preferences.

Figure 20-2 OBED Properties Window


20

Default NodeUse this field to specify which object you want to be the root of the viewdisplayed in OBED. This allows you to display a specific portion of the MIThierarchy.

ScopeThis field is used to specify how far down in the MIT hierarchy the displayreaches. The default is two levels down. The scope is entered as a numericvalue <n>, where <n> is the number of levels down from the root you want todisplay.

CMIS FilterEnter a CMIS filter in this field to restrict the number of objects displayed inthe MIT hierarchy in OBED.

Note – A filter consists of at least one assertion (item ) about the presence(present ) or values (equality , greaterOrEqual , lessOrEqual ,substrings ) of attributes in objects being tested. If a filter involves more thanone assertion, the assertions can be grouped using and , or , and not . Filters canbe arbitrarily complex, as you can nest filters within filters. For information onbuilding CMIS filters, refer to Appendix D, “CMIS Scoping and Filtering.”

Show Objects WithThis field allows you to show the objects with their Fully Distinguished Names(FDN) or Relative Distinguished Names (RDN). The default is RDN. For moreinformation on FDNs and RDNs, see the “Configuring SNMP Trap Handling”chapter in the Solstice Enterprise Manager Administration Guide.

Object Configuration WindowThis field allows you to specify the number of Object Configuration windowsOBED can bring up at any given time. The default is Multiple, allowing OBEDto display a new window every time you:

• Double click on an object

• Select Object ➤ Get from the menu bar on a highlighted object


20

ButtonsThe five buttons at the bottom of the Default Preferences window are:

• OK—causes your selections to take effect and dismisses the DefaultPreferences window

• Apply—causes your selections to take effect, but does not dismiss theDefault Preferences window

• Cancel—dismisses the Default Preferences window without implementingthe indicated choices

• Default—restores the default values for OBED properties

• Help—accesses the online help information about the current window

20.4.2 Exit

Select File ➤ Exit to leave the Object Editor application.

20.5 Object MenuThe selections on this menu are active or grayed out, depending upon thenumber of objects selected and whether or not you specified multiple windowsin the Object Configuration Window field of the Default Preferences window:

• If no objects are selected, then the Create option is active, but all otheroptions are grayed out.

• If one object is selected, then the Get, Create, Delete, and Deselect optionsare active. The Action option may or may not be active, depending uponwhether or not any actions are available for the selected object.

• If more than one object is selected, and:• If Multiple is selected in the Object Configuration Window field, the Get,

Delete, and Deselect options are active, but the Action and Create optionsare grayed out. Selecting the Get option causes one Object Configurationwindow (Figure 20-6) to appear for each selected object. Alternatively, youcan double-click on any selected object to bring up an ObjectConfiguration window for that object.


20

• If Single is selected in the Object Configuration Window field, the Deleteand Deselect options are active, but the Get, Action, and Create optionsare grayed out. To bring up an Object Configuration window for a selectedobject, you must double-click on that object.

Selecting the Object menu displays the pull-down menu options describedbelow.

20.5.1 Get...

Select Object ➤ Get to load and display attribute information about aparticular object. To do so, select that object so that it is highlighted, then selectGet from the Object pull-down menu. This invokes the Object Configurationdialogue window, shown in Figure 20-3.


20

Figure 20-3 Object Configuration Window

You can also initiate a Get operation by double-clicking the object in the OBEDnavigator.

For a detailed description of the Object Configuration Window, seeSection 20.6, “Object Configuration Window.”


20

20.5.2 Action

Select Object ➤ Action to display a list of possible actions, which aredetermined by the class of the selected object. If no actions for the selectedobject are available, the Action option is grayed out.

The Action option provides a pull-right menu (Figure 20-4) listing the possibleactions for the selected object. After you select a particular action, the Actiondialogue box appears (Figure 20-5). The name of the selected action will befilled in. After filling in the required parameter, select OK to implement theaction. An OBED Output Window appears with the results of the action.


20

Figure 20-4 Action Pull-Right Menu


20

Figure 20-5 Action Dialogue Window

20.5.3 Create...

Select Object ➤ Create to display the Object Configuration window(Figure 20-6), which allows you to create an object in the MIS.


20


If an object is selected, the attribute-value pairs of the currently selected objectare displayed for creating a new object of the same class. In this case, the newobject inherits all of the properties of the selected object except for those thatmust be different.


20

Note – In OBED, you are always adding or modifying one object at a time, thatis, one leaf in the MIT. An object is an instance of a GDMO class definition thatexists in the MIS. This is different from an application such as the Viewer, inwhich the graphic representation of an object represents a group of objects,among them a topology object; a map object; and one or more managedobjects, which tell the MIS which protocol to use and how to accessmanagement data for a particular object.

20.5.4 Delete

Select Object ➤ Delete to delete all currently selected objects. A dialog boxappears asking you to confirm this operation. Click the OK button to delete theselected objects.

Upon object deletion, the number of objects deleted are reported in the bottomright-hand corner of the main window.

20.5.5 Deselect

Select Object ➤ Deselect to deselect all currently selected objects.

20.6 Object Configuration WindowSelect Object ➤ Get to open the Object Configuration window (Figure 20-7).


20


This window contains the areas described below.


20

Object Loaded AreaThis area, at the top of the window, shows the object FDN, its parent FDN, andits object class.

Attributes AreaThe middle area of the window shows the attribute/value pairs pertaining tothe currently loaded object(s). The window resize buttons at the right top andbottom of this area enable you to adjust the size of this area, with the total sizeof the window remaining constant.

A change to any of the fields in the attribute area causes the Set button tobecome active. However, some of the fields in the attribute area are read-only:

• If you try to change a read-only field and click on the Set button, thechanges do not take effect, and the original values are restored. You do notreceive any error messages.

• If you try to change a writable field but your change(s) contains asyntactical error, you receive an error dialog box.

Notice that some of the fields are very long and extend beyond the boundariesof the window. For those fields, you can position the mouse cursor in the fieldand click on the third mouse button to retrieve a pull-down menu with thefollowing options:

• Expand

• Collapse

Select Expand to see the field in an expanded and formatted form. The fieldwill include scroll bars along the bottom and right sides. Select Collapse toreturn the field to its original, unformatted state.

If you make a change to a field, you must click on the Set button to save thechange before you expand the field. If you try to expand a field that you havechanged but have not saved, you will receive a warning message stating thatyour changes will be lost.

Attribute Format AreaWhen you select an attribute in the attribute area, the ASN.1 type of theselected attribute is displayed in the Attribute Format area.


20

Message AreaThe area at the bottom of the window is used to display messages, such aswhen an attribute value change event is received.

The Object Configuration Window is used either during object Creation orduring a Get/Set operation. If you select an object before invoking a Create orGet operation, the window is displayed with the complete set ofattribute/value pairs of the selected object. The Set or Create button at thebottom of the window remains grayed out until your new attribute values areadded or the existing ones modified.

20.6.1 Buttons

The buttons at the bottom of the Object Configuration Window are explainedbelow.

Set (or Create)This button is:

• Grayed out when the Object Configuration window is first invoked

• Labeled “Create” if the Object Configuration window is invoked from theObject ➤ Create menu option

To make changes to attributes of the selected object:

1. Enter the changes in the attribute value field (for example, changing thevalue of topoNodeSeverity from 50 to 30. This causes the Set button tobecome active.

2. Click on the Set button

UpdateThis button becomes active if events occur for this object while the ObjectConfiguration window is in use. If you select Update, the values in theattribute area of the Object Configuration window will be updated with thechanged values.

CloseSelect this button to exit from the Object Configuration window.


20

20.7 Using the Object Editor to Access the Objectsin a CMIP Agent

The em_oct -cmip command, which invokes the CMIP Configurationwindow, is used to tell the MIS about the CMIP Agents in your system. (Thiscommand replaces the em_cmipconfig command from the previous release ofSolstice EM.) Apart from the addressing information for each CMIP Agent, youalso tell the MIS about the top level object in the CMIP agent. This is also thename of the object, beneath Root, in the MIS Management Information Tree(MIT) where the objects supported by the CMIP Agent will appear.

When the Object Editor starts, it issues a single request to the MIS for all theobjects in the MIS MIT whose parent is Root. Some of these objects willactually reside in CMIP Agents. The MIS takes the single request that theObject Editor issues and in turn issues a separate request to each CMIP agent,the local MIS, and any remote MISs.

The only information that the MIS has about the object contained by Root ineach remote system, MIS, or CMIP agent, is the name you provided using theCMIP Configuration window. It does not know the corresponding object classof this object. As CMIP requires that both an object name and object class areprovided, the MIS uses a wildcard for object class in the requests that it sendsto the remote systems. This wildcard is called Actual Class, as defined in ITUX.722. The remote system interprets the object class set to Actual Class as if theobject class of the target of the operation were specified.

Thus, CMIP agents should support Actual Class. However, your CMIP agentmay not support Actual Class. In this case, the Object Editor can be configuredso that its requests always use the real object class, rather that the wildcard(Actual Class). There is a similar facility for application developers using thePMI.

To configure the Object Editor, select File ➤ Properties to bring up theProperties window, and fill in a value for the Default Node field. This will beidentical to the Distinguished Name that you entered when configuring theCMIP agent. After the node has been entered, append :OC:< BMOC> to theend, where <BMOC> is the object class corresponding to the DistinguishedName that you just entered.


20

For example, if the Distinguished Name that you entered when configuring aCMIP agent was:

This is an instance of the network Managed Object Class. You would enter thefollowing in the Default Node field:

Click on either the OK or Apply button, and the Object Editor will display theobjects present in the CMIP agent that you specified.

/networkId=pString:"Network-1"

/networkId=pString:"Network-1":OC:network

21-1

Topology Import/Export Tool 21

21.1 OverviewThe Topology Import/Export Tool allows you to export all or part of thetopology node hierarchy and associated agent objects (CMIP agents, RPCagents, and SNMP agents) on a connected MIS to a file in ASCII format. Thisfile can then be imported to other MISs in order to re-create the topology nodehierarchy that existed on the original system.

The Topology Import/Export Tool is used:

• As a backup-and-restore utility for topology-related information, so that inthe event that the Solstice EM database is lost (for example, a file systemcrash), you will be able to restore this information by importing the file

Note – The Topology Import/Export Tool is to be used whenever automaticgeneration of a specific topology hierarchy is desired. It is not to be used as abackup tool, since only topology-related information is saved during an export,and not the entire MIS database.

Overview page 21-1

Starting the Topology Import/Export Tool page 21-2

Using the Topology Import/Export Tool page 21-4


21

• As an object migration utility, meaning that you can export topology-relateddata from an older version of the MIS and import it into a newer version ofthe MIS. Currently, the following migration paths are supported:• From 1.1.1 to 1.1.1• From 1.1.1 to 2.0• From 1.2 to 1.2• From 1.2 to 2.0• From 2.0 to 2.0

• As an object replication tool, meaning that you can copy the topologydatabase from one MIS to another MIS for data redundancy.

In addition to exporting the entire topology database, the Solstice EM 2.0version of the Topology Import/Export Tool supports a “container export”feature. This feature allows you specify a container and export the topologynodes within and beneath that container in the view hierarchy. Along with thetopology nodes, all of the associated agent objects (CMIP, RPC, and SNMPagents) and FDN tables are also exported. Similarly, the “container import”feature allows you to import a file that contains the container export data. Youmust assign a “parent” node for the container you want to import.

21.2 Starting the Topology Import/Export ToolStart the Topology Import/Export Tool from the command line as follows:

You will be prompted to enter your login ID and password. Your access to theTopology Import/Export tool’s functions depends on the permissions grantedto you. For more information about granting permissions, see Chapter 9,“Access Manager.”

You must specify one out of the -export , -import , or -clear parametersalong with the -file < filename> parameter. The -export parameter is used tospecify an export operation, the -import parameter is used to specify animport operation, and the -clear parameter is used to clear and import anMIS.

hostname% em_topoimex -file < filename> -export | -import | -clear [options]

Topology Import/Export Tool 21-3

21

Note – The -clear option does not delete the topoType data from the targetMIS. However, if you make any changes in the exported file, then import thatfile using the -clear option, the topoType data in the target MIS will reflectthese changes.

The optional parameters for the em_topoimex command are described below

To export all topology-related information in the MIS to a file calledtopo_db_info , use command shown below.

Similarly, to import a file called topo_db_info which contains exportedtopology information, use command shown below.

Option Description

-help Print list of options (with descriptions) for theem_topoimex command.

-host < hostname> Specify a remote MIS server.

-c < container> Specify a <container> to export (implies -export ).

-debug Display debugging information.

-m < mis_name> Specify the MIS from which you want to exportinformation.

-parent < parent_name> Specify the <parent_name> for the container youwant to import (implies -import ).

-quiet Specify quiet mode, meaning that no questions areasked for the -clear or -import options.

hostname% em_topoimex -file topo_db_info -export

hostname% em_topoimex -file topo_db_info -import


21

21.3 Using the Topology Import/Export ToolIt is recommended that the export and import operations be performed whilethe target MIS is not processing other transactions/requests. The export andimport operations do not correct inconsistencies that may occur due to ongoingMIS activity during the import/export operations.

The exported MIS information will:

• Be stored in a file in ASCII format

• Be editable so that scripts can generate it

• Allow for manual editing

• Be interchangeable between HP-UX and Solaris Platforms

If more than one topology database exists (due to MIS-MIS communication),then the export operation will provide various export options:

• An option to export topology branches from an MIS that can be reachedfrom the local MIS

• An option to export a particular container within a topology branch from aparticular MIS (All objects under that node will be exported.)

In situations where a non-unique topoNodeName container object is specified,the export tool prompts you to select the proper one.

21.3.1 Exported Information

The data that will be exported will be all of the attributes within the specifiedobject types. This includes all objects within the following branches of the MIS:

• topoTypeDB—all topoTypeNodes

• topoNodeDB—topoNodes (Each topoNode will be identified within theexport data by its topoNodeId.)

• topoViewDB—all topoNodes (This data must be associated with itscorresponding topoNode within the export data.)

• topoViewNodeDB—all topoViewNodes (This data must be correctlyassociated with its parent topoView, and with its corresponding topoNode.)

• internetClassId=...—SNMP agent objects (This object must be associatedwith each topoNode object that references it.)

Topology Import/Export Tool 21-5

21

• agentTableType=”RPC”—RPC agent objects (This object must be associatedwith each corresponding topoNode object.)

• agentTableType=”CMIP”—CMIP agent objects (This object must beassociated with each topoNode object that references it.)

• subsystemId=”EM-MIS”—FDN table

The exported information will be stored in an ASCII file

21.3.2 Not Exported Information

Any information not specified in the list in Section 21.3.1, “ExportedInformation,” will not be exported. This includes the following types ofinformation:

• Request data—emApplicationType=”Collection,” andemApplicationType=”NerveCenter”

• Log Data

• User-defined managed objects


21

22-1

Automatic Management 22

22.1 OverviewAutomatic Management allows you to configure the MIS to:

• Launch new requests automatically when objects that satisfy user-configurable criteria are created

• Stop requests automatically when objects of the specified type are deleted

The Automatic Management feature of EM contains two software components:

• User-configurable autoManagementEntry objects which provide the criterianecessary to select objects to be managed and indicate the Nerve Centerrequest templates to be launched against each object. By default, the MISalso contains an autoManagement object that is created when the MIS isstarted. This is the container object for the autoManagementEntry objects.

Overview page 22-1

Default autoManagementEntry Objects page 22-2

Creating autoManagementEntry Objects page 22-3

Using OBED to Start/Stop Automatic Management page 22-6

Automatic Management Daemon (em_autod) page 22-7


22

• An automanagement daemon (em_autod ), responsible for monitoring thecreation and deletion of objects in the MIS, starting requests for newlycreated objects, and stopping requests when objects are deleted

The autoManagement object is created automatically when the MIS is startedusing either the em_services -i or em_services -r command. However,you will need to create one or more autoManagementEntry objects to be able toactivate automatic management. You need to create one such object for eachNerve Center request that you want to be launched automatically against aselected group of devices.

After creating the autoManagementEntry objects, use the Object Editor toactivated or deactivated them as described in Section 22.4, “Using OBED toStart/Stop Automatic Management.” The automatic management daemon alsomust have been started in order for the automatic management function to beenabled, as described in Section 22.5, “Automatic Management Daemon(em_autod).”

22.2 Default autoManagementEntry ObjectsBy default, three autoManagementEntry objects are shipped with the package.During the installation procedure, you have the option of creating these threeautoManagementEntry objects in $EM_HOME/install/automgt . For moreinformation, see the Solstice Enterprise Manager Installation Guide.

The three autoManagementEntry objects are:

• admin_oper_status_up.autoentry (AdminOperStatusUp template)

• device_reachable_ping.autoentry (DeviceReachablePing template)

• link_up.autoentry (LinkUp template)

If you elect to not create these autoManagementEntry objects duringinstallation, you can create them at any time using the guidelines specifiedbelow.

Automatic Management 22-3

22

22.3 Creating autoManagementEntry ObjectsTo create an autoManagementEntry object, use the following command in ashell:

You will need to use this command to load an <entry-file> for theautoManagementEntry objects you wish to create. Multiple CREATE entriescan be present in the <entry-file> to load multiple autoManagementEntryobjects. The format of CREATE entries is illustrated in the example below.

The following <entry-file>, when loaded using the command above, creates asingle auto management entry that launches the IsSnmpSystemUp_Hosttemplate against all topology objects on the local MIS of type “Host” which areconfigured to manage SNMP.

The fields in the <entry-file> are described below:

• OC—The name of the object class

• OI—The identity or distinguished name of this auto management entry.Each entry should have a unique name.

• autoEntryTemplate—Specifies the name of the template that is to belaunched against the topology object. This template must exist in thesystem. To view the request templates, use the Request Designer. (For moreinformation, see the “Request Designer” chapter in the Solstice EnterpriseManager Administration Guide.

# em_objop -f < entry-file>

CREATE{OC = autoManagementEntryOI = 'subsystemId="EM-MIS"/autoManagerId="TheAutoManager"/autoEntryId="IsSnmpSystemUp_Host"'autoEntryTemplate = IsSnmpSystemUpautoEntryScope = localautoEntryTopoType = HostautoEntryKey = 'cmipsnmp'}


22

• autoEntryScope—Specifies whether or not the requests are launched againstall topology nodes. The possible values for this attribute are:• local• all

If the autoEntryScope is set to local, and there are multiple MISs connected,then the specified autoEntryTemplate is launched against only thosetopology nodes in the local MIS. If autoEntryObject is set to all, then therequest is launched against all topology nodes in all available MISs.

• autoEntryTopoType—Specifies the topology type of the objects againstwhich you want to launch the request(s). This must be a valid topologytype. All topology types in Solstice EM begin with a capital letter (forexample, “Host”, not “host”).

Note – Auto Management only works for objects which exist in the topology.

• autoEntryKey—The value specified in this field must match a keywordcontained in the ObjectInstance in the topoNodeMOSet before a request islaunched. If you specify 'none', then em_autod launches requests withoutchecking the topoNodeMOSet. In short, requests are started on topologynode creation based on topology type. This allows for very simple automanagement entries. The default value ‘none’.

New autoManagementEntry objects can be created at any time. Anotherexample of a CREATE entry is shown below.

The following CREATE entry creates a single auto management entry thatlaunches the LinkUp_Link template against all topology objects on the localMIS of type “Link” with ‘1 3 6 1 4 1 42 2 2 2 9 1 1 3 6 1 2 1 2’ as part of itstopoNodeMOSEt.

CREATE{OC = autoManagementEntryOI = 'subsystemId="EM-MIS"/autoManagerId="TheAutoManager"/autoEntryId="LinkUp_Link"'autoEntryTemplate = LinkUpautoEntryScope = localautoEntryTopoType = LinkautoEntryKey = '1 3 6 1 4 1 42 2 2 2 9 1 1 3 6 1 2 1 2'}


22

You can also create an auto management entry that takes advantage of SunNetManager (SNM) RPC-based proxy agents. A Management station may initiatepolling by issuing SNM requests to proxy agents. This means that the actualpolling is done outside the MIS by the proxy agent, thus minimizing thenetwork traffic and polling work required of the MIS. For example, you couldsend a request to a proxy agent to check devices for reachability. If a device isnot reachable, then that proxy agent sends out an event notification. For moreinformation, see the “Device Management Using RPC Agents” chapter in theSolstice Enterprise Manager Administration Guide.

To take advantage of this feature, add the following attributes to the CREATEentry:

• autoEntrySchema—A concatenation of the SNM agent name and the groupin the schema that the agent supports

• autoEntryEventRequest—This is the snmEventRequest information, enteredin the same format used for the RCL function snmEventRequest whenbuilding a BC request template. For more information, see the “RCLFunctions” chapter in the Solstice Enterprise Manager Administration Guide.

The following <entry-file> creates a single auto management entry thatlaunches the Ping-Reachable_Host template against all topology objects on thelocal MIS of type “Host” whose topoNodeMOSet contains the string “RPC”.All devices meeting this criteria will have an RPC eventRequestActionlaunched against it with the argument specified in the autoEntryEventRequestattribute.


22

Note – The keyword “HOSTNAME” in the autoEntryEventRequest attribute isreplaced by the name of the host against which the request is launched.

The advantage of this type of auto management entry is that you only needone template for any number of hosts. All the threshold checking is done bythe SNM RPC proxy agent.

22.4 Using OBED to Start/Stop Automatic ManagementTo activate or de-activate the auto management function, use the Object Editor(OBED) to change the administrativeState attribute for anyautoManagementEntry object:

1. Start the Object Editor

2. Open the subsystemId=”EM_MIS” folder

3. Select the autoManagerId=”TheAutoManager” object

4. Select the autoManagementEntry object(s) you want to change

5. Select Object ➤ Get from the menu bar to invoke the Object Configurationwindow

When autoManagementEntry objects are first created in the MIS, they aregiven an administrativeState value of unlocked , which means that automanagement is turned on. If you change the administrativeState value tolocked , the auto management entry is disabled and all requests launched by

CREATE{OC = autoManagementEntryOI = 'subsystemId="EM-MIS"/autoManagerId="TheAutoManager"/autoEntryId="Ping-Reachable_Host"'autoEntryTemplate = AutoManageDecayReachablePingautoEntryScope = localautoEntryTopoType = HostautoEntryKey = RPCautoEntrySchema = ping-reachautoEntryEventRequest = 'request: {agentHost "HOSTNAME",agentProgram 100115, agentVersion10,timeout 33,interval 30, group "reach", threshold {"reachable",21,1,"0",high}}'}


22

the auto management daemon for that entry are deleted. If you wish to re-enable the auto management entry, you need to change the administrativeStateattribute value to unlocked .

To change the value, type the desired value in the Object Configurationwindow administrativeState field, press Return, then click on the Set button toimplement the change.

If you want to create an autoManagementEntry object but do not want to startautomatic management until later, you can insert the following line into theCREATE entry:

Then, when you are ready to launch the requests, use OBED to change theadministrativeState to unlocked.

Changing the administrativeState value for an auto management object enablesauto management for the objects selected by that entry, but only if the automanagement daemon is running.

22.5 Automatic Management Daemon (em_autod )The auto management daemon (em_autod ) is the process responsible forstarting and stopping requests launched against managed objects when theautomatic management function is active. The daemon can be started at anytime after start-up of the MIS. The command for starting the daemon is:

The optional -debug parameter causes debugging information to bedisplayed.

After it is started, the daemon retrieves the auto management object from theMIS and derives an album of all autoManagementEntry objects. For eachautoManagementEntry object, em_autod retrieves the managed objects fromthe MIS that pass the filter criteria set up in that autoManagementEntry. Therequest template specified by the entry is launched against all objects thusderived for that entry.

administrativeState = locked

# em_autod [-debug]


22

The auto management daemon registers with the MIS to receive eventnotifications for creation or deletion of objects. If an object is created in the MISthat matches the selection criteria of a given autoManagementEntry, thedaemon launches the request specified by that entry against that object.

The auto management daemon is also notified by the MIS if theadministrativeState value is changed for any autoManagementEntry, or if anymanaged objects are deleted. If the value of administrativeState for a givenautoManagementEntry is changed from unlocked to locked , the daemondeletes the requests that were launched against the objects selected by thatentry.

If a request that is launched against an object is deleted manually, you can re-start automatic management for that object by first changing theadministrativeState to locked , then changing it to unlocked .

Note – There can be at most one em_autod daemon running at one time. TheMIS does not check for duplicate auto management daemons.

23-1

Command Line Options 23

23.1 OverviewThis chapter contains a description of the command line options available forall Solstice EM applications and utilities, as well as a description of theiroptional parameters. By default, the applications and utilities are located in$EM_HOME/bin. The applications and utilities are arranged in alphabeticalorder.

Before invoking any GUI application from the command line, be sure that the$XFILESEARCHPATH environment variable is set. If you installed Solstice EMin the default location, it should point to /opt/SUNWconn/em/config/%N . Ifthis environment variable is not set, the fonts, colors, and backgrounds maynot be displayed correctly.

Any time you start an application from the command line, and you are a non-root user, you might receive a Login window, depending upon whether or notpassword authentication is turned on. To proceed, enter your password andclick OK. Your access to the application’s functions depends on thepermissions granted to you through Access Control. For more informationabout password authentication and granting permissions, see Chapter 9,“Access Manager.”

Overview page 23-1

Command Line Options page 23-2


23

For any application that accepts the optional -host < hostname> parameter, youcan specify a machine name, a domain name, or an IP address.

23.2 Command Line Options

23.2.1 em Command

The em command starts the Application Launcher, which is a GUI applicationthat allows you to start other applications provided with the Solstice EMproduct, as well as third-party applications. For more information, seeChapter 8, “Application Launcher.”

Start the Application Launcher from the command line as follows:

The optional parameters for the em command are described in Table 23-1.

You can also start the Application Launcher and connect to a remote MIS bysetting the $EM_SERVER environment variable to the name of the remote hostwhere the MIS is running, and then invoking the em command with nooptions.

23.2.2 em_accesscmd Command

The em_accesscmd command starts the Access Control application, which is anon-GUI application used to create access control objects and assign privileges.

Third-party application developers must first use em_accesscmd to definetheir application, then use either em_accesscmd or em_accessmgr to createaccess control objects and assign privileges.


Table 23-1 em Command Line Options

Option Description

-help Print list of options (with descriptions) for the emcommand.


Command Line Options 23-3

23

23.2.2.1 Starting the Access Control Application

As root , start the Access Control application from the command line asfollows:

The optional parameters for the em_accesscmd command are described inTable 23-2.

If you start the Access Manager using the -import option, the file you want toimport should contain a series of commands that you want to be executed.These commands are described below in Section 23.2.2.2, “CommandsSupported by the Access Control Application.”

If you start the Access Control application without using the -import option,you must create access control objects and assign privileges from the commandline. There are a variety of commands available for you to use. But first, a fewsyntactical items to note:

• No quotes are required for the <login_name> option and the :ALL option.Quotes are required for all other options.

• The + character following an option means that you can enter multipleinstances of that option. The delimiter is a space.

23.2.2.2 Commands Supported by the AccessControl Application

The Access Control application supports the following commands:

# em_accesscmd [-help] [-host < hostname>] [-import < filename>]

Table 23-2 em_accesscmd Command Line Options

Option Description


-help Print list of options (with descriptions) for theem_accesscmd command.

-import <filename> Specify the name of a file to import.


23

createUser < login_name> "< full_name>"This command is used to create a user.

createGroup "< group_name>" "< description>"This command is used to create a group.

createApplication "< app_name>" "< description>"This command is used to create an application. Privileges can not beassigned to use the application unless it is created.

createFeature "< app_name>" "< feature_name>" "< description>"This command is used to create an application feature.

addMembers "< group_name>" < login_name>+This command is used to add users to a group. One or more login namesseparated by spaces can be specified. The login names should not be inquotes.

assignApps "< group_name>" [ :ALL | "< app_name>"+]This command is used to assign applications to a group. If :ALL is specified,then all applications are assigned to the group. Otherwise, one or moreapplications must be specified. All features (if any) of the specifiedapplications are implicitely assigned to the group.

assignAppFeatures "< group_name>" "< app_name>" ["< feature_name>"]+This command is used to assign application features to a group.

Note – The <feature_name> option defaults to all features if none are entered.

deleteUser < login_name>This command is used to delete a user. The user will first be removed fromall the groups he/she belongs to.

deleteGroup "< group_name>"This command is used to delete a group. The users belonging to the groupare not deleted.

deleteApplication "< app_name>"This command is used to delete an application. An application cannot bedeleted unless its features (if any) are deleted first.

deleteFeature "< app_name>" "< feature_name>"This command is used to delete an application feature.


23

removeMembers "< group_name>" < login_name>+This command is used to remove users from a group. The users are notdeleted.

deassignApps "< group_name>" [ :ALL | "< app_name>"+ ]This command is used to deassign applications from a group. If :ALL isspecified, then all applications are deassigned from the group. Otherwise,one or more applications must be specified. All features (if any) of theseapplications are implicitely deassigned from the group.

deassignAppFeatures "< group_name>" "< app_name>"["< feature_name>"]+

This command is used to deassign application features from a group.

Note – The <feature_name> option defaults to all features if none are entered.

getAuthFeatures [ < login_name> [ "< app_name>"+ ] ]This command is used to get the list of authorized features for the givenuser and the given applications. If no login name isspecified, then thecurrently logged in user is assumed and no application names can bespecified. If the login name is given, then any number of application namescan be specified. If no applications are specified, then the authorizedfeatures for all applications are listed.

getAuthApps [< login_name>]This command is used to get the list of authorized applications for the givenuser. If no login name is specified, then the currently logged in user isassumed.

23.2.3 em_accessmgr Command

The em_accessmgr command starts Access Manager, which is a GUIapplication used to control access to Solstice EM applications. For moreinformation, see Chapter 9, “Access Manager.”

As root , start the Access Manager from the command line as follows:

# em_accessmgr [-help] [-host < hostname>] &


23

The optional parameters for the em_accessmgr command are described inTable 23-3.

23.2.4 em_alarmmgr Command

The em_alarmmgr command starts the Alarm Manager, which is a GUIapplication used to provide information concerning alarms received by theMIS. For more information, see Chapter 15, “Alarm Manager.”

Start the Alarm Manager from the command line as follows:

The optional parameters for the em_alarmmgr command are described inTable 23-4.

Table 23-3 em_accessmgr Command Line Options

Option Description

-help Print list of options (with descriptions) for theem_accessmgr command.


hostname% em_alarmmgr [options] &

Table 23-4 em_alarmmgr Command Line Options

Option Description

-help Print list of options (with descriptions) for theem_alarmmgr command.


-device <device_name> Specify the device name.

-refresh <refresh_rate> Specify the screen refresh rate in milliseconds.

-log <log_name> Specify the log name as MIS_name:Log_name .

-file <config_file> Specify the filter configuration file.


23

23.2.5 em_asn1 Command

The em_asn1 command is used to invoke the ASN.1 compiler, which is used tocompile the contents of ASN.1 documents into a format used internally by theMIS. For more information, see the “Adding a Managed Object to the MIS”chapter of the Solstice Enterprise Manager Administration Guide, or Chapter 3,“Compilers.”

Invoke the ANS.1 compiler from the command line as follows:

The optional parameters for the em_asn1 command are described inTable 23-5.

23.2.6 em_autod Daemon

The em_autod daemon is a UNIX process used for monitoring the creationand deletion of objects in the MIS, starting requests for newly created objects,and stopping requests when objects are deleted. For more information, seeChapter 22, “Automatic Management.”

Invoke the em_autod daemon from the command line as follows:

hostname% em_asn1 [-v] [-o < output_dir>] < file>...

Table 23-5 em_asn1 Command Line Options

Option Description

-help Print list of options (with descriptions) for the em_asn1command.

-v Specify verbose mode.

-o < output_dir> Specify the directory into which the compiled files are to bewritten. The directory will be created if it does not alreadyexist.

<file> Specify the name of the ASN.1 document to be compiled.Multiple file names may be specified, delimited by a space.

hostname% em_autod [-help] [-debug]


23

The optional parameters for the em_autod daemon are described in Table 23-6.

This daemon is started automatically whenever the em_services command isinvoked.

23.2.7 em_cmib2gdmo Command

The em_cmib2gdmo command invokes the Concise MIB compiler, which isused to translate a managed object description written in the Concise MIBformat into both GDMO and ASN.1 formats, thus serving as a preprocessor forboth the GDMO and ASN.1 compilers. For more information, see Chapter 3,“Compilers.”

Invoke the Concise MIB compiler from the command line as follows:

The optional parameters for the em_cmib2gdmo command are described inTable 23-7.

Table 23-6 em_autod Command Line Options

Option Description

-help Print list of options (with descriptions) for the em_autoddaemon.


hostname% em_cmib2gdmo [options] < file>...

Table 23-7 em_cmib2gdmo Command Line Options

Option Description

-help Print list of options (with descriptions) for the em_cmib2gdmocommand.

-b Include CMIB descriptions in Behavior clauses.

-d Display debugging information.

-1155 Do not include OIDs from RFC 1155.

-l Generate GDMO and ASN.1 files for the last specified MIBonly.


23

23.2.8 em_cmip Daemon

The em_cmip daemon is a UNIX process used to implement CMIP MPAfunctions. For more information, see Chapter 2, “Management InformationServer (MIS),” and the “Configuring Communication with CMIP Agents”chapter in the Solstice Enterprise Manager Administration Guide.

Invoke the em_cmip daemon from the command line as follows:


23.2.9 em_compose_all Command

The em_compose_all command takes a GDMO file as input, and:

• Reads all the object classes and name bindings in the GDMO definition file

• Composes and loads the name bindings accordingly in the MIS.

Prior to running this command, the GDMO file should have been loaded intothe MDR using the GDMO compiler em_gdmo.

Invoke the em_compose_all command from the command line as follows:

-p Do not generate parsible behaviors the GDMO table entryMOCs.

-t Do not perform typechecking.

-w Do not print warnings.

<file>... Specify the name of the document to be compiled. Multiple filenames may be specified, delimited by a space.

hostname% em_cmip &

hostname% em_compose_all < filename>

Table 23-7 em_cmib2gdmo Command Line Options

Option Description


23

You must specify the name of a GDMO document.

23.2.10 em_compose_oc Command

The em_compose_oc command is used to instantiate a new object class withvolatile data storage. Volatile data storage means that if the MIS is restarted(with the em_services command but without the -i option), any object ofthe object class which was composed with the em_compose_oc command willnot be in the MIS after it is restarted.

Before running this command, the Managed Object Class should have beenloaded into the MDR using the GDMO compiler em_gdmo and the ASN.1compiler em_asn1 .

Invoke the em_compose_oc command from the command line as follows:

The arguments for the em_compose_oc command are one or more objectclasses from the GDMO file.

23.2.11 em_compose_poc Command

The em_compose_poc command is used to instantiate a new object class withpersistent data storage. Persistent data storage means that if the MIS isrestarted (with the em_services command but without the -i option), anyobject of the object class which was composed with the em_compose_occommand will remain in the MIS after it is restarted.

Note – If the MIS is restarted using em_services -i , then all persistentstorage is lost.

Before running this command, the Managed Object Class should have beenloaded into the MDR using the GDMO compiler em_gdmo and the ASN.1compiler em_asn1 .

hostname% em_compose_oc < object_class> ...


23

Invoke the em_compose_poc command from the command line as follows:

The arguments for the em_compose_poc command are one or more objectclasses from the GDMO file.

23.2.12 em_datacollector Command

The em_datacollector command starts the Data Collector, which is a GUIapplication used to configure Data Collection Entry objects and display thedata gathered from requests. For more information, see Chapter 12, “DataCollector.”

Start the Data Collector from the command line as follows:

The optional parameters for the em_datacollector command are describedin Table 23-8.

23.2.13 em_datad Daemon

The em_datad daemon is a UNIX process that can be configured by the DataCollector application to collect performance and accounting data. For moreinformation, see Chapter 12, “Data Collector.”

Invoke the em_datad daemon from the command line as follows:

hostname% em_compose_poc < object_class>

hostname% em_datacollector [-help] [-host < hostname>] &

Table 23-8 em_datacollector Command Line Options

Option Description

-help Print list of options (with descriptions) for theem_datacollector command.


hostname% em_datad [-help] [-host < hostname>] [-debug] &


23

The optional parameters for the em_datad daemon are described in Table 23-9.


23.2.14 em_dataviewer Command

The em_dataviewer command starts the Data Viewer, which is a GUIapplication enabling you to get, view, modify, and set managementinformation for CMIP and SNM managed objects. For more information, seeChapter 17, “Data Viewer.”

Start the Data Viewer from the command line as follows:

The optional parameters for the em_dataviewer command are described inTable 23-10.

Table 23-9 em_datad Command Line Options

Option Description

-help Print list of options (with descriptions) for theem_datad daemon.


-debug Print debugging information.

hostname% em_dataviewer [options] &

Table 23-10em_dataviewer Command Line Options

Option Description

-help Print list of options (with descriptions) for theem_dataviewer command.


-o <object> Specify the object you want to view.

-id <topo_id> Specify the toponode ID of the object you want toview.


23

23.2.15 em_debug Command

23.2.15.1 Overview of em_debug

The em_debug command supports the Solstice EM remote dynamic debuggingfeature. This command must be invoked only while the MIS is running. TheMIS contains various debug agents which aid in sending out the relevantdebugging information to the requestor. Some of these agents are enabledstatically (for example, misc_stdout ), meaning that they are already enabledwhen the MIS is started. The rest of the debugging agents (for example,oammsg_debug) are disabled statically, and you must enable these agentsdynamically with the em_debug command. The MIS also contains a debugserver, which is part of the PMI. The debug server listens for requests from thedebug client (em_debug) and services those requests.

Debug agents that are statically enabled will send the debug information toeither stdout or stderr , depending on which debug macro was used todeclare the debug agent. The $EM_HOME/include/pmi/debug.hh file lists allof the various macros that can be used to instantiate the debugging agents.These macros basically allow you to specify either stdout or stderr as theplace for the debugging agent to send the information.

Debugging agents that are started using the em_debug command send theiroutput to the window from which the em_debug command was invoked. Thisdiffers from the earlier versions of em_debug (pldebug ), which sent its outputto the window from which the MIS was started.

The em_debug utility allows multiple users to debug the same MISsimultaneously.

23.2.15.2 Using em_debug

Start the em_debug program from the command line as follows:

hostname% em_debug [option] -c “[on|off] < agent>”


23

The optional parameters for the em_debug command are described inTable 23-11.

To terminate a running em_debug session, use the kill command to kill it, ortype Ctrl-C.

Shown below are some common debugging agents defined for the-c "[on|off] < agent>" parameter:

Table 23-11em_debug Command Line Options

Option Description

-help Print list of options (with descriptions) for theem_debug command.

-host < hostname> Specify the <hostname> of a remote MIS that youwant to debug.

-p < port> Specify the debug port number. This is useful onlywhen multiple MISs are running on a single host,or when the default debug port used by MIS ischanged.

Table 23-12em_debug Debug Agents

Agent Description

actmsg_debug

Print PMI Action request and response messages.

oammsg_debug

Print PMI non-Action messages, that is, Get, Set, Create,Delete, Cancel-Get and Event requests and responses.

asn_debug Print debug messages on ASN1 modules processing.

asn_info Print detailed debug messages on ASN1 modulesprocessing.

cmip_debug Print CMIP Over TCP/IP debug messages, including acse ,rose , lpp and tcp .

cmip_info Print detailed debug messages on CMIP Over TCP/IP.

snmp_debug Print SNMP PDM debug messages.

snmp_info Print detailed SNMP PDM debug messages.

rpc_debug Print RPC PDM debug messages.

rpc_info Print detailed RPC PDM messages.


23

To turn off a debugging agent that you have turned on, use the-c “[on|off] < agent>” parameter. For example, suppose that you arerunning the MIS locally, and turn on the oammsg_debug agent as follows:

To turn off the oammsg_debug agent, issue the command shown below from awindow other than the one in which you turned on the oammsg_debug agent.

You can use standard UNIX regular expressions to start and/or stop multipledebugging agents. For example, to start all agents beginning with the letters“rpc”, enter the following command:

The ability to use regular expressions allows you to turn on all availabledebugging agents by entering the following command:

Each debugging agent is listed as it is turned on. Currently, there is no methodof listing all available debugging agents in the MIS without turning all of themon. You must rely on the documents of appropriate libraries (like NCI or PMI)or other sources.

In addition to the agents listed in Table 23-12, you can refer to the “BuildingRequest Templates” chapter in the Solstice Enterprise Manager AdministrationGuide for information on Nerve Center debugging agents.

Also, refer to the “RCL Functions” chapter in the Solstice Enterprise ManagerAdministration Guide for information on using the Request Condition Language(RCL) print() function to send debugging messages to stdout .

Currently, em_debug is a primitive command line interface (CLI) for which asophisticated GUI may be provided in future.

hostname% em_debug -c "on oammsg_debug"

hostname% em_debug -c "off oammsg_debug"

hostname% em_debug -c "on rpc*"

hostname% em_debug -c "on *"


23

23.2.16 em_discover Command

The em_discover command starts Discover, which is a GUI application usedto add managed objects to the MIS database. For more information, seeChapter 11, “Discover.”

Start Discover from the command line as follows:

The optional parameters for the em_discover command are described inTable 23-13.

hostname% em_discover [options] &

Table 23-13em_discover Command LIne Options

Option Description

-help Print list of options (with descriptions) for theem_discover command.


-arp Discover devices on subnets by using acombination of ARP Tables and ICMP echorequests (pinging).

-cr < string> [:< string>] Specify up to five SNMP read community strings,delimited by a colon. Default is “public”.

-cw < string> Specify the SNMP write community string.Default is “private”.

-device < device_name> Discover only the specified device.

-g [only] < gateway> Probe the specified gateway(s) first, then rest ofnetwork. Multiple gateways are delimited by acolon. If “only” is used, Discover stops afterprobing the specified gateway(s).

-hop < n> Specify the number of hops that Discover willfollow. Default is 0. Specify -1 for an unlimitedsearch.

-mask < n> Specify the netmask to be used for discoverypurposes.


23

23.2.16.1 The Monitor Function

You can also start the Monitor Function using the em_discover command.

-net < network> Specify a specific subnetwork or non-subnettednetwork to discover. The maximum hop count fora subnetwork other than the local one is 0.

-objects < object> Specify object type(s) to discover. Multiple objectsare delimited by a colon.

-pb Causes Discover to use a broadcast method ofpinging in probing subnetworks.

-pfn ( num> Specify the maximum number of outstandingsimultaneous pings per interval specified by -pftoption. The default value is 10.

-pfr < num> Specify the number of times Discover tries tocontact a device using ICMP (ping) when thedefault serial ping method is used.

-pft < seconds> Specify the frequency between transmissions ofICMP echo requests (in seconds) when the defaultserial ping method is used.

-pr < num> Specify the number of times Discover tries tocontact a device using ICMP (ping).

-r < from:to> Specify a range of host addresses to ping for eachspecified network/subnet.

-S < n> Specify a range of host addresses to ping for eachspecified network/subnet.

-T Start the Discover GUI.

-t < seconds> Set the ICMP (ping) timeout value.

-flat Create discovered objects in a flat hierarchy.

-wait Instructs Discover to wait for a platformconnection at start-up.

-www Notify when discovered device is a WWW server(uses ports 80 and 8080).

Table 23-13em_discover Command LIne Options

Option Description


23

The Monitor function provides a GUI used to regularly update the MISdatabase.

Start the Monitor function from the command line as follows:

The optional parameters for the em_discover command used to start theMonitor function are described in Table 23-14.

hostname% em_discover -M [options] &

Table 23-14Monitor Command Line Options

Option Description

-contain < container> Specify the name of the container into which all newlydiscovered objects are placed.

-ct < time> Specify the cycle time in minutes.

-h < holding_area> Specify the name of a holding area into which allnewly discovered objects are placed.

-fc < container> Limits Monitor’s search operations and reachabilitytesting to devices in the specified <container>. Multiplecontainer names are delimited by a colon.

-i < device> Ignores the specified <device>. Multiple device namesare delimited by a colon.

-lh Activate the log monitor history feature.

-lf < filename> Specify the name of the log monitor history file.

-m < address> Mail log monitor history file to specified <address>.

-start < hh:mm> Specify start time <hh:mm>

-stop < hh:mm> Specify stop time <hh:mm>

-startd < mm/dd/yy> Specify a start date <mm/dd/yy>.

-stopd < mm/dd/yy> Specify a stop date <mm/dd/yy>.

-w Run Monitor weekly.


23

23.2.16.2 Discover’s Debugging Feature

Discover also features debugging, available only through the command line.Start the debugging feature from the command line as follows:

There are two forms of debugging available.

• The options in Table 23-15 allow you to receive detailed information aboutthe discovery process that is being executed, and run a full discover processand thus establish a connection with the MIS.

• The options in Table 23-16 allow you to start specific software modules thatare components of Discover, but will have no effect on the MIS itself as noMIS connection will be made.

hostname% em_discover -D [options] &

Table 23-15Discover Debugging Command Line Options

Option Description

n Prints debugging information about the discovery process in aformat that is understandable to the average user

e Prints debugging information about the discovery process in aformat that assumes Internet-specific expertise

Table 23-16Discover Debugging Command Line Options

Option Description

c Starts Discover’s Configuration module, which printsinformation about the host on which Discover is running, suchas local routing table, ARP table, interfaces, default routers,network number, subnet number, and netmask

s < hostname> Starts Discover’s SNMP module, which takes <hostname> as itstarget host, does a one-time SNMP query of the specifieddevice, and prints the information to standard output

t < hostname> Starts Discover’s Traceroutes module, which executes thetraceroutes code with <hostname> as target, and prints theroute to the specified host along with the gateways to get thereto the standard output.


23

23.2.17 em_gdmo Command

The em_gdmo command invokes the GDMO compiler, which is used to extendthe capabilities of the Solstice EM MIS to deal with new classes of objects notpreviously known to it. It does this by compiling GDMO descriptions ofmanaged objects, which are provided in GDMO documents. For moreinformation, see the “Adding a Managed Object to the MIS” chapter in theSolstice Enterprise Manager Administration Guide, or Chapter 3, “Compilers.”

Invoke the GDMO compiler from the command line as follows:

The -file < file> parameter is used to specify the input file(s). The optionalparameters for the em_gdmo command are described in Table 23-17.

The GDMO compiler functions in two modes of operation:

• Parse-only

• Parse-and-compile

hostname% em_gdmo [options] -file < file>...

Table 23-17em_gdmo Command Line Options

Option Description

-help Print list of options (with descriptions) for theem_gdmo command.

-host < server> Specify the name of an MIS server. The compileddefinitions are loaded into the MDR.

-header < string> Specify the header string.

-verbose Specify verbose mode.

-debug Display MIS debugging information.

-parse Specify parse-only operation.

-output < output_dir> Specify the directory into which the compiled files areto be written.


23

23.2.17.1 Parse-only Operation

Invoke the GDMO compiler for parse-only operation as follows:

23.2.17.2 Parse-and-Compile Operation

Once the input files can be parsed without error, you can run the compiler inthe parse-and-compile mode:

You then must run em_services t o load the definitions into the MDR.Alternatively, you can load the definitions into the MDR directly:

23.2.18 em_grapher Command

The em_grapher command starts the Grapher, which is a GUI applicationused to view alarm information in a graphical format. For more information,see Chapter 18, “Grapher.”

Start the Grapher from the command line as follows:

23.2.19 em_help Command

The em_help command starts the Solstice EM online help application.

Start the online help application from the command line as follows:

hostname% em_gdmo -parse -file < file>...

hostname% em_gdmo -file < file>...

hostname% em_gdmo -host < hostname> -file < file>...

hostname% em_grapher &

hostname% em_help &


23

23.2.20 em_imex Command

The em_imex command can be used to import or export log objects from or toan ASCII file. This command is invoked from the Log Manager application byselecting either File ➤ Import File or File ➤ Export to File from the LogManager menu bar, or from the command line as shown below. For moreinformation, see Chapter 13, “Log Manager.”

Invoke the em_imex command from the command line as follows:

The optional parameters for the em_imex command are described inTable 23-18.

23.2.21 em_load_name_bindings Command

The em_load_name_bindings command loads the name bindings, which tellthe MIS where the object is in the MIT. Prior to running this command:

• The GDMO definitions should be loaded into the MDR using the GDMOcompiler em_gdmo.

• The ASN1 definitions should be loaded into MDR using the ASN.1 compilerem_asn1 .

• The object classes used in the name binding should have been composedusing em_compose_oc or em_compose_poc .

hostname% em_imex [options] &

Table 23-18em_imex Command Line Options

Option Description

-help Print list of options (with descriptions) for the em_imexcommand.


-c Send creates in import mode.

-e < moi> Specify the managed object to export.

-f < filename> Specify the name of the file to read or create.

-t < log|topo> Specify the type of operation.


23

Invoke the em_load_name_bindings command from the command line asfollows:

The command line arguments for the em_load_name_bindings commandare one or more name bindings from the GDMO file.

23.2.22 em_load_nc_templates Command

The em_load_nc_templates command is a UNIX script that invokes theem_ncimport -file command for each file in the$EM_HOME/install/nc_templates directory. If you create some NerveCenter templates, you can either load them manually using theem_ncimport -file command, or you can add this template to the$EM_HOME/install/nc_templates directory, then invoke theem_load_nc_templates command. For more information, seeSection 23.2.30, “em_ncimport Command.”

Invoke the em_load_nc_templates command from the command line asfollows:

23.2.23 em_log2rdb.< database> Daemon

The em_log2rdb daemon is a UNIX process that reads, translates, andtransfers historical log files to a specified database. For more information abouthistorical relational database (RDB) logging, see Chapter 5, “LogManagement.”

Start the Historical RDB Logging daemon from the command line as follows:

hostname% em_load_name_bindings < name_binding> ...

hostname% em_load_nc_templates &

hostname% em_log2rdb.< database> [-std] [-c < config_file>]


23

The <.database> parameter is the extension implemented for one of threedatabases: Sybase, Oracle, and Informix. For these three databases, theem_log2rdb .<database> commands are em_log2rdb.sybs ,em_log2rdb.orcl , and em_log2rdb.ifmx , respectively. The optionalparameters for the em_log2rdb.< database> command are described inTable 23-19.

23.2.24 em_login Daemon

The em_login daemon is a UNIX process that listens to all connection requestsfor password authentication. For more information, see Chapter 2,“Management Information Server (MIS).”

Invoke the em_login daemon from the command line as follows:


23.2.25 em_logmgr Command

The em_logmgr command starts the Log Manager, which is a GUI applicationused to create, modify, and delete log objects. For more information, seeChapter 13, “Log Manager.”

Table 23-19em_log2rdb.< database> Command Line Options

Option Description

-help Print list of options (with descriptions) for theem_log2rdb.< database> command.

-s Instructs the daemon to terminate the processing ofhistorical log files after one pass through

-t Trace the SQL.

-d Drop all existing database tables.

-c < config_file> Specify the configuration file name. This will override thedefault configuration file.

hostname% em_login [-help] &


23

Start the Log Manager from the command line as follows:

The optional parameters for the em_logmgr command are described inTable 23-20.

23.2.26 em_logview Command

The em_logview command starts the Log Viewer, which is a GUI applicationused to browse the contents of logs or log objects, and view the details of logrecords. For more information, see Chapter 14, “Log Viewer.”

Start the Log Viewer from the command line as follows:

hostname% em_logmgr [options] &

Table 23-20em_logmgr Command Line Options

Option Description



-c < config_file> Specify the <filename> of the configuration file.

-logobj < fdn> Display the log objects of the MIS specified in <fdn> in themain window summary table.

-logrec < fdn> Same as -logobj . This option is for compatibility with theLog Viewer application.

hostname% em_logview [options] &


23

The optional parameters for the em_logview command are described inTable 23-21.

23.2.27 em_mismgr Command

The em_mismgr command starts the MIS Manager, a GUI application used toconfigure cooperative management among EM management stations, and isused to set up and take down CMIP connections between one ManagementInformation Server and another. For more information, see Chapter 7, “MIS toMIS Communication.”

Start the MIS Manager from the command line as follows:

The optional parameters for theem_mismgr command are described in Table 23-22.

Table 23-21em_logview Command Line Options

Option Description




-logobj < fdn> Display the log records of the specified log objects in themain window summary table.

-logrec < fdn> Displays the log in which the log record appears (same as-logobj ) and, in addition, displays the log recordspecified as fdn as the selected log record.

hostname% em_mismgr [options] &

Table 23-22em_mismgr Command Line Options

Option Description



-port < port> Specify the port number (default is 5555).


23

23.2.28 em_ncam Daemon

The em_ncam daemon is a UNIX process that handles Nerve Center actionssuch as sending e-mail or executing a UNIX command. For more information,see Chapter 2, “Management Information Server (MIS),” or the “Nerve CenterOverview” chapter in the Solstice Enterprise Manager Administration Guide forinformation about the Nerve Center.

Start the em_ncam daemon from the command line as follows


23.2.29 em_ncexport Command

The em_ncexport command starts the Nerve Center Export utility, which is anon-GUI application used to export Nerve Center templates and objects to anASCII file. For more information, see the “Request Designer” chapter in theSolstice Enterprise Manager Administration Guide.

Start the Nerve Center Export utility from the command line as follows:

-break Break the connection.

-remote < remote_MIS> Specify the remote MIS.

-discrim < discriminator> Specify the discriminator construct. Default is“and:{} ”.

hostname% em_ncam [-help]

hostname% em_ncexport [options]

Table 23-22em_mismgr Command Line Options

Option Description


23

The optional parameters for theem_ncexport command are described inTable 23-23.

23.2.30 em_ncimport Command

The em_ncimport command starts the Nerve Center Import utility, which is anon-GUI application used to import data previously exported by the NerveCenter Export utility. For more information, see the “Request Designer”chapter in the Solstice Enterprise Manager Administration Guide.

Start the Nerve Center Import utility from the command line as follows:

Table 23-23em_ncexport Command Line Options

Option Description

-help Print list of options (with descriptions) forthe em_ncexport command.


-file < file> Specify the <file> to which exported datashould be written. Default is standardoutput.

-template [< template>...] Specify the template(s) to export. Delimiter isa space for multiple templates. Default is alltemplates and all objects referenced by thosetemplates.

-condition [< condition>...] Specify the condition(s) to export. Delimiteris a space for multiple conditions. Default isall conditions.

-pollrate [< pollrate>...] Specify the pollrate(s) to export. Delimiter isa space for multiple pollrates. Default is allpollrates.

-severity [< severity>...] Specify the severity(s) to export. Delimiter isa space for multiple severities. Default is allseverities.

-minimize Prevents the automatic export of all objectsreferenced by the exported templates.

hostname% em_ncimport [options]


23

The optional parameters for theem_ncimport command are described inTable 23-24.

23.2.31 em_nnadd Command

The em_nnadd command starts the Nickname Service Addition utility, whichis used to add a global nickname server to the MIS. By default, this is doneautomatically when Enterprise Manager is started.

Start the Nickname Service Addition utility from the command line as follows:

Table 23-24em_ncimport Command Line Options

Option Description

-help Print list of options (with descriptions) forthe em_ncimport command.


-file < file> Specify the <file> to which exported datashould be written. Default is standardoutput.

-template [< template>...] Specify the template(s) to export. Delimiter isa space for multiple templates. Default is alltemplates and all objects referenced by thosetemplates.

-condition [< condition>...] Specify the condition(s) to export. Delimiteris a space for multiple conditions. Default isall conditions.

-pollrate [< pollrate>...] Specify the pollrate(s) to export. Delimiter isa space for multiple pollrates. Default is allpollrates.

-severity [< severity>...] Specify the severity(s) to export. Delimiter isa space for multiple severities. Default is allseverities.

-verbose Print all warnings and reports.

hostname% em_nnadd [options]


23

The optional parameters for theem_nnadd command are described in Table 23-25.

For more detailed information about creating and adding nicknames (FDNtranslation), see the “Developing EM Solutions” chapter in the SolsticeEnterprise Manager Application Development Guide.

23.2.32 em_nnconfig Command

The em_nnconfig starts the Nickname Service Configuration utility, which isused to populate the global nickname server. This utility reads a file describingthe nicknames (FDN translations) you want to add to the global nicknameserver.

Start the Nickname Service Configuration utility from the command line asfollows:

The file represented by <filename> should consist of one or more lines of theformat:

Table 23-25em_nnadd Command LIne Options

Option Description



-m < mpa_host> Specify the name of the nickname server.

-n < port> Specify the port number (default is 5555).

hostname% em_nnconfig < filename>

FDNTranslated text to be substituted


23

Table 23-26 shows a sample file that can be read as input for the em_nnconfigcommand:


23.2.33 em_nnmpa Command

The em_nnmpa daemon is a UNIX process that starts the global nickname(FDN translation) server, which is a mapping engine that maps object names(FDNs) into user-defined text. (For detailed information on FDNs, refer to the“Configuring SNMP Trap Handling” chapter in the Solstice Enterprise ManagerAdministration Guide.) The idea is that whenever you encounter an FDN, forexample, /systemId=name:”fashion”/logId=string:”AlarmLog” , youcan instead be presented with more readable definition, like “Default AlarmLog.” Currently the Alarm Manager and Log Manager utilize the globalnickname server.

Table 23-26Sample Input File for em_nnconfig

# This is a sample em_nnconfig input file

# Entries are organized in pairs of lines

# The first line is the FDN

# The next non blank/comment line is assumed to be the nickname/FDNTranslation

{ {{ systemId, “mis_machine” }} }

Nickname-for-top-level_object

{ {{ systemId, “mis_machine” }}, {{ logId, “AlarmLog”}} }

Nickname-for-first-level-object

# Comments can be inserted, e.g. This complete line is a comment

{ {{ systemId, “mis_machine” }}, {{ subsystemId, “EM-MIS”}}}

Nickname-for-another-first-level-object


23

It is up to you to populate the nickname server with mappings. Theem_nnconfig utility is available to help you do this.

Furthermore, this functionality is implemented as a Management ProtocolAdaptor, or MPA. (See Chapter 4, “Management Protocol Support,” for moreinformation on MPAs.) In order for an MIS to access an MPA, the MIS must be"configured" to be made aware of the MPA. The em_nnadd utility is used to dothis after the MIS is started. If other MISs want to share a single MPA (asopposed to each having their own), they can use this utility to accomplish it.



23.2.34 em_obcodegen Command

The em_obcodegen command starts the Object Code Generator (OCG), whichis used to generate object behavior code from GDMO and ASN.1 definitions.For more information, see the "Developing Object Behaviors" chapter in theSolstice Enterprise Manager Application Development Guide.

Start the OCG from the command line as follows:

You must specify a valid managed object class loaded in Solstice EM MISwhich is currently running on your localhost . The optional parameters forthe em_obcodegen command are described in Table 23-27.

hostname% em_obcodegen [options] < object_class> &

Table 23-27em_obcodegen Command Line Options

Option Description

-help Print list of options (with descriptions) for theem_obcodegen command.

-debug Print debugging information while OCG is running

-info Print error, warning, and information messages whileOCG is running. This is the default behavior.


23

23.2.35 em_obed Command

The em_oct command starts the Object Editor (OBED), which is a GUIapplication that allows you to view any of the objects in a Solstice EM MIS’sManagement Information Tree (MIT). For more information, see Chapter 20,“Object Editor/Browser.”

Start OBED from the command line as follows:

The optional parameters for the em_obed command are described inTable 23-28.

23.2.36 em_objop Command

The em_objop command starts a UNIX utility that allows you to sendCREATE, SET, DERIVE, and DELETE requests to an MIS from a command lineor from a file. It is primarily used by init_platform to create and modifyobjects at MIS startup. It may be useful in situations where you want tomanipulate the object tree (that is, the configuration) but don’t want to use anapplication or write a program.

Invoke the em_objop utility from the command line as follows:

hostname% em_obed [options] &

Table 23-28em_obed Command Line Options

Option Description

-help Print list of options (with descriptions) for theem_obed command.


-scope < num_levels> Specify the number of levels down in the MIThierarchy the display will reach. The default is 2.

-root < FDN> Specify the FDN of the object you want to be the rootof the view displayed in OBED.

hostname% em_objop -f < operations_file>


23

You must specify the <operations_file>, which is the ASCII file containing theoperations to be performed. Two such files are init_platform , a file read byem_objop for platform initialization using em_services -i , andrestart_platform , also read by em_objop for platform restart usingem_services . Both of these files reside (by default) in the$EM_HOME/etc/install/em_platform directory.

23.2.37 em_oct Command

The em_oct command starts the Object Configuration Tool (OCT), which is aGUI application that allows you to configure and browse the attributes of amanaged object in the Viewer. For more information, see Chapter 19, “ObjectConfiguration Tool.”

Start OCT from the command line as follows:

The optional parameters for the em_oct command are described inTable 23-29.

hostname% em_oct [options] &

Table 23-29em_oct Command Line Options

Option Description

-help Print list of options (with descriptions) for the em_octcommand.


-cmip Configure a CMIP object. Replaces em_cmipconfig .

-id < id>... Specify topology IDs. Multiple IDs are delimited by aspace.

-link < id1> < id2> Create a link between <id1> and <id2>.

-mis Configure an MIS object.

-name < name>... Specify the name of an object. Multiple names aredelimited by a space.

-parent < parent_id> Specify the parent of the object you want to create.


23

23.2.38 em_reqedit Command

The em_reqedit command is used to start the Request Designer, a GUIapplication that allows you to create request templates. For more information,see the “Request Designer” chapter in the Solstice Enterprise ManagerAdministration Guide.

Start the Request Designer from the command line as follows:

The optional parameters for the em_reqedit command are described inTable 23-30.

23.2.39 em_services Command

The em_services command is used to start or restart the MIS and itsassociated daemons. For more information, see Chapter 2, “ManagementInformation Server (MIS).”

-rpc Configure an RPC object.

-snmp Configure an SNMP object.

-type < type> Specify the topology type of the object you want tocreate.

hostname% em_reqedit [-host < hostname>] [-t < template>] [-help]

Table 23-30em_reqedit Command Line Options

Option Description

-help Print list of options (with descriptions) for theem_reqedit command.


-t < template> Specify the name of the template you want to load.

Table 23-29em_oct Command Line Options

Option Description


23

As root , invoke the em_services command from the command line asfollows:

The optional parameters for the em_services command are described inTable 23-31.

23.2.40 em_snm_type_import Command

The em_snm_type_import command is a utility used to import new SunNetManager (SNM) types (as defined in the specified schema file) into the SolsticeEM environment.This utility:

• Updates the file $EM_HOME/config/SNM2EM_type_mapping

• Creates or updates the file $EM_HOME/install/em_platform/bc_map

• Updates the file $EM_HOME/config/em_viewer.cf

For more information, see the “SunNet Manager Application Support” chapterin the Solstice Enterprise Manager Administration Guide.

Invoke this command from the command line as follows:

# em_services [-help] [-i] [-r] [-s] &

Table 23-31em_services Command Line Options

Option Description

no option(s) Start or restart the MIS in the state in which it was lastshutdown.

-help Print list of options (with descriptions) for the em_servicescommand.

-i Start or restart the MIS with a new database.

-r Start or restart and reinitialize the MIS.

-s Kill all daemons.

hostname% em_snm_type_import -file < snm_schema_file>...


23

You must use the -file < snm_schema_file> parameter to specify one or moreschema files, delimited by a space.

23.2.41 em_snmdb_import Command

The em_snmdb_import command is a UNIX utility used to import a SunNetManager (SNM) topology database into Solstice EM’s runtime database.

Invoke this command from the command line as follows:

The -import < snm_db_file> parameter is used to specify the file name of theSNM database you want to import. The optional parameters for theem_snmdb_import command are described in Table 23-32.

23.2.42 em_snm2gdmo Command

The em_snm2gdmo command invokes the Schema compiler, which is used totranslate SNM 2.2 or later schema files into GDMO descriptions used inSolstice EM. For more information, see Chapter 3, “Compilers.”

Invoke the Schema compiler from the command line as follows:

The <OID_branch> parameter is any unused OID branch number for thespecified schema file. This number is used to assign a unique OID to everyrecord type defined within the specified schema file. “0” and “1” are the onlyOID branch numbers that are already reserved:

hostname% em_snmdb_import [options] -import < snm_db_file>

Table 23-32em_snmdb_import Command Line Options

Option Description

-help Print list of options (with descriptions) for theem_snmdb_import command.


hostname% em_snm2gdmo < filename> < OID_branch> &


23

• “0” is reserved for SNM agent/proxy schemas, which can be found in$SNM_HOME/agents.

• “1” is reserved specifically for the schema file elements.schema .

See Chapter 3, “Compilers,” for more information on determining which OIDbranch numbers are available or reserved.

23.2.43 em_snmfwd Daemon

The em_snmfwd daemon is a UNIX process that forwards SunNet Manager(SNM) events to the MIS for processing. For more information, see Chapter 2,“Management Information Server (MIS),” or the “Device Management UsingSunNet Manager Agents” chapter in the Solstice Enterprise ManagerAdministration Guide.

Invoke the em_snmfwd daemon from the command line as follows:

The optional parameters for the em_snmfwd command are described inTable 23-33.


hostname% em_snmfwd [-host < hostname>] [-debug] &

Table 23-33em_snmfwd Command Line Options

Option Description

-help Print list of options (with descriptions) for theem_snmfwd command.


-debug Print debugging information.


23

23.2.44 em_snmpbrowser Command

The em_snmpbrowser command starts the SNMP Browser, which is a GUIapplication used to retrieve, view, modify, and set attributes and attributevalues for SNMP MIBs managed by Solstice EM. For more information, seeChapter 16, “SNMP Browser.”

Start the SNMP Browser from the command line as follows:

The optional parameters for the em_snmpbrowser command are described inTable 23-34.

23.2.45 em_topoimex Command

The em_topoimex command starts the Topology Import/Export Tool, which isa non-GUI application used to export all or part of the topology node hierarchyon one or more connected MISs to a file in ASCII format. This file can then beimported to other MISs in order to re-create the topology node hierarchy thatexisted on the original system. For more information, see Chapter 21,“Topology Import/Export Tool.”

hostname% em_snmpbrowser [options] &

Table 23-34em_snmpbrowser Command Line Options

Option Description

-help Print list of options (with descriptions) for theem_snmpbrowser command.


-agent < agentname> Specify the default agent name. If omitted, default isthe name of the MIS host.

-community < string> Specify the default community string. If omitted,default is “public”.

-id < topo_id> Specify the topoNodeId. This option overrides -agentIf the two options are used together.


23

Start the Topology Import/Export Tool from the command line as follows:

You must specify one out of the -export , -import , or -clear parametersalong with the -file < filename> parameter. The -export parameter is used tospecify an export operation, the -import parameter is used to specify animport operation, and the -clear parameter is used to clear and import anMIS.

Note – The -clear option does not delete the topoType data from the targetMIS. However, if you make any changes in the exported file, then import thatfile using the -clear option, the topoType data in the target MIS will reflectthese changes.

The optional parameters for the em_topoimex command are described inTable 23-35.

hostname% em_topoimex -file < file> -export | -import | -clear [options] &

Table 23-35em_topoimex Command Line Options

Option Description

-help Print list of options (with descriptions) for theem_topoimex command.

-host < hostname> Specify a remote MIS server.

-c < container> Specify a <container> to export (implies -export ).


-m < mis_name> Specify the MIS from which you want to exportinformation.

-parent < parent_name> Specify the <parent_name> for the container youwant to import (implies -import ).

-quiet Specify quiet mode, meaning that no questions areasked for the -clear or -import options.


23

23.2.46 em_viewer Command

The em_viewer command starts the Viewer, which is a GUI applicationenabling you to create, inspect, and monitor a view, which is a graphicalrepresentation of a set of related managed objects. For more information, seeChapter 10, “Viewer.”

Start the Viewer from the command line as follows:

The optional parameters for the em_viewer command are described inTable 23-36.

hostname% em_viewer [options] &

Table 23-36em_viewer Command Line Options

Option Description

-help Print list of options (with descriptions) for theem_viewer command.

-host < hostname> Specify a remote machine where the MIS is running.

-no_move Object movement not allowed.

-r Do not initialize requests.

-view < view> Initial view.

-no_labels Do not display the object labels.

-no_scale Do not resize the object labels on zoom.

-ifont < fontname> Use the specified <fontname> for object labels.


23

A-1

Standard Event Notifications A

Agents located on devices in the network typically are designed to generatereports to managers on their own initiative when certain conditions aredetected; these messages are called event notifications.

Notifications are defined for managed objects in accordance with the ITU X.722Guidelines for the Definition of Managed Object (GDMO) standard. The MISacquires knowledge of event notification types when the pertinent GDMOdocuments are loaded into the MIS at startup. The CMIP event notificationsdefined in EM by default are the following:

Defined by the ITU X.722 Defintion of Management Information (DMI)standard:

• objectCreation• objectDeletion• attributeValueChange• relationshipChange• stateChange• communicationsAlarm• environmentalAlarm• equipmentAlarm• integrityViolation• operationalViolation• physicalViolation• processingErrorAlarm• qualityofServiceAlarm• securityServiceOrMechanismAlarm

A-2 Solstice Enterprise Manager Reference Manual

A

• timeDomainViolation

Defined by the ISO-Internet Management Co-existence (IIMC) standard:

• internetAlarm

Solstice EM-specific event notifications:

• snmAlarmEvent• snmAlarmTrap• nerveCenterAlarm• coldStartTrap• warmStartTrap• linkDownTrap• linkUpTrap• authenticationFailureTrap• egpNeighborLossTrap• enterpriseSpecificTrap

The structures of these event notifications is described below.

nerveCenterAlarmsThe NerveCenterAlarmInfo type is defined in the file/opt/SUNWconn/em/etc/asn1/nc.asn1.The nerveCenterAlarm notification is defined in the file/opt/SUNWconn/em/etc/gdmo/gdmo.asn1.

Table A-1 nerveCenterAlarm Attributes

Attribute Name Values Required/Optional

perceivedSeverity ENUMERATED● indeterminate (0)● critical (1)● major (2)● minor (3)● warning (4)● cleared (5)

Required

additionalText GraphicString Optional

mosiSeverity INTEGER Required

mosiStateID INTEGER Required

Standard Event Notifications A-3

A

internetAlarmsThe InternetAlarmInfo type is defined in the file/opt/SUNWconn/em/etc/asn1/IimcCommonDef.asn1.The notification is defined in the file/opt/SUNWconn/em/etc/iimcManagementDoc-1.gdmo.

Table A-2 internetAlarm Attributes


probableCause CHOICE● globalValue (snmpTrapOID)● localValue (INTEGER)

Required

attributeIdList SET OF attributeIds derived fromcomponents of variable bindings

Optional

objectInstanceList SET OF Object Instancesassociated with variable bindings

Optional

unknownVarBindList CHOICE of● SEQUENCE of untranslatedSNMP v1 variable bindings● SEQUENCE of untranslatedSNMP v2 variable bindings

Optional

internetTrapInfo SET OF SEQUENCE of objectinstances, and attributes andvalues, in variable bindings

Optional


Optional

notificationId INTEGER Optional

correlatedNot SET OF SEQUENCE of correlatednotificationIds (INTEGER) andsource Object Instances

Optional

transportDomain Object Identifier for the transportprotocol associated with theagent that sent the alarm

Optional


A

OSI X.733 AlarmsThe CMIP event notifications defined by the ITU X.733 ISO/IEC 10164-4standard are the following:

• communicationsAlarm• environmentalAlarm• equipmentAlarm• qualityofServiceAlarm• processingErrorAlarm

These notifications and their attributes are defined in the following files:

/opt/SUNWconn/em/etc/gdmo/dmi.gdmo/opt/SUNWconn/em/etc/asn1/dmi.asn1

The dmi.asn1 file defines the AlarmInfo type.

transportAddress OCTET STRING containing thetransport layer address of theagent that issued the trap

Optional

accessControlInfo CHOICE of● communityString● partyInfo, which is aSEQUENCE of:— srcParty (Object Identifier)— dstParty (Object Identifer)— context (Object Identifier)

Optional

additionalInformation SET OF SEQUENCE● Object Identifier● BOOLEAN● ANY DEFINED BY <identifier>

additionalText GrasphicString Optional

Table A-2 internetAlarm Attributes



A

The attributes of these event notifications are described in Table A-3.

Table A-3 X.733 OSI Alarms


probableCause CHOICE of● globalValue (ObjectIdentifier)● localValue (INTEGER)

Required

specificProblems [1] SET OF CHOICE of● Object Identifier● INTEGER

Optional


Required

backedUpStatus BOOLEAN (true if backed up) Optional

backUpObject [2] CHOICE of● ObjectInstance (objectName)● NULL (no object)

Optional

trendIndication [3] ENUMERATED● lessSevere (0)● noChange (1)● moreSevere (2)

Optional


A

thresholdInfo [4] SEQUENCE of● attribudeId (triggeredthreshold)● observed value CHOICE of— INTEGER— REAL● Optional CHOICE of— up (SEQUENCE of high andoptional low values, each ofwhich is a CHOICE of REAL orINTEGER)— down (SEQUENCE of highand low values, each of whichis a CHOICE of REAL orINTEGER)● Optional GeneralizedTime(armTime)

Optional

notificationIdentifier [5] INTEGER Optional

correlatedNotifications [6] SET OF SEQUENCE of● SET of INTEGERs(correlatedNotifications)● Object Instance (source)

Optional

stateChangeDefinition [7] SET OF SEQUENCE of● attributeId● Optional oldAttributeValue(ANY DEFINED BY<identifier>)● newAttributeValue (ANYDEFINED BY <identifier>)

Optional

monitoredAttributes [8] SET OF Attribute Optional




A

CMIP Security AlarmsThe CMIP security alarms are described in Table A-4. These notifications aredefined in the file/opt/SUNWconn/em/etc/gdmo/dmi.gdmo

The SecurityAlarmInfo type is defined in the file/opt/SUNWconn/em/etc/asn1/dmi.asn1

proposedRepairActions [9] SET OF CHOICE of● Object Identifier● INTEGER

Optional


additionalInformation [10] SET OF SEQUENCE of● Object Identifier● BOOLEAN (default false)● information (ANY DEFINEDBY <identifier>)

Optional

Table A-4 CMIP Security Alarms

Atttribute Name Values Required/Optional

securityAlarmCause Object Identifier Required

securityAlarmSeverity ENUMERATED● indeterminate (0)● critical (1)● major (2)● minor (3)● warning (4)● cleared (5)

Required

securityAlarmDetector CHOICE of● Object Identifer(mechanism)● Object Instance (object)● AE-title (application)

Required




A

snmAlarmEventssnmAlarmEvents are used to translate SunNet Manager events into CMIPevent notifications. snmAlarmEvents — described in Table A-5. — are definedin /opt/SUNWconn/em/etc/gdmo/mpa.gdmo.

This notification defintion uses the AlarmInfo type which is defined in the file/opt/SUNWconn/em/etc/asn1/dmi.asn1.

serviceUser SEQUENCE of● Object Identifier● ANY DEFINED BY<identifier>

Required

serviceProvider SEQUENCE of● Object Identifier● ANY DEFINED BY<identifier>

Required

notificationIdentifier INTEGER Optional

correleatedNotifications SET OF SEQUENCE of● SET OF INTEGER(notificationIds)● Object Instance (source)

Optional


additionalInformation SET OF SEQUENCE of● Object Identifier● BOOLEAN (default false)● ANY DEFINED BY<identifier>

Optional

Table A-4 CMIP Security Alarms

Atttribute Name Values Required/Optional


A

Table A-5 snmAlarmEvents


probableCause CHOICE of● globalValue (Object Identifier)● localValue (INTEGER)

Required

specificProblems SET OF CHOICE of● Object Identifier● INTEGER

Optional


Required

backedUpStatus BOOLEAN (true if backed up) Optional

backUpObject CHOICE of● ObjectInstance● NULL (no object)

Optional

trendIndication ENUMERATED● lessSevere (0)● noChange (1)● moreSevere (2)

Optional


A

thresholdInfo SEQUENCE of● attribudeId (triggeredthreshold)● observed value CHOICE of— INTEGER— REAL● Optional CHOICE of— up (SEQUENCE of high andoptional low values, each ofwhich is a CHOICE of REAL orINTEGER)— down (SEQUENCE of highand low values, each of which isa CHOICE of REAL or INTEGER)● Optional GeneralizedTime(armTime)

Optional


correlatedNotifications SET OF SEQUENCE of● SET OF INTEGER(notificationIds)● Object Instance (source)

Optional

stateChangeDefinition SET OF SEQUENCE of● attributeId● Optional oldAttributeValue(ANY DEFINED BY <identifier>)● newAttributeValue (ANYDEFINED BY <identifier>)

Optional

monitoredAttributes SET OF Attribute Optional

proposedRepairActions SET OF CHOICE of● Object Identifier● INTEGER

Optional


additionalInformation SET OF SEQUENCE of● Object Identifier● BOOLEAN (default false)● ANY DEFINED BY <identifier>

Optional

Table A-5 snmAlarmEvents



A

objectDeletion and objectCreation Event NotificationsobjectDelection and objectCreation event notifications are defined in the file:/opt/SUNWconn/em/etc/gdmo/dmi.gdmo

The ObjectInfo type is defined in the file/opt/SUNWconn/em/etc/asn1/dmi.asn1

attributeValueChange Event NotificationattributeValueChange event notifications — described in Table A-7 — aredefined in the file:/opt/SUNWconn/em/etc/gdmo/dmi.gdmo

The AttributeValueChangeInfo type is defined in the file/opt/SUNWconn/em/etc/asn1/dmi.asn1

Table A-6 objectDeletion and objectCreation Event Notifications


sourceIndicator ENUMERATEDresourceOperation (0)managementOperation (1)unknown (2)

Optional

attributeList SET OF attributeIds Optional



Optional



Optional


A

relationshipChange Event NotificationrelationshipChange event notifications — described in Table A-8 — are definedin the following documents:/opt/SUNWconn/em/etc/gdmo/dmi.gdmo

The RelationshipChangeInfo type is defined in the file/opt/SUNWconn/em/etc/asn1/dmi.asn1

Table A-7 attributeValueChange Event Notification



Optional

attributeIdentifierList SET OF attributeIds Optional

attributeValueChangeDefinition SET OF SEQUENCE of● attributeId● Optional oldAttributeValue(ANY DEFINED BY <addtributeId>)● newAttributeValue (ANYDEFINED BY <attributeId>)

Required



Optional



Optional


A

stateChange Event NotificationsstateChange event notifications are defined in the following documents:/opt/SUNWconn/em/etc/gdmo/dmi.gdmo

Table A-8 relationshipChange Event Notification

Attribute Name Value Required/Optional


Optional


relationshipChangeDefinition SET OF SEQUENCE of● attributeId● OptionaloldAttributeValue (ANYDEFINED BY <addtributeId>)● newAttributeValue (ANYDEFINED BY <attributeId>)

Required



Optional


additionalInformation SET OF SEQUENCE of● Object Identifier● BOOLEAN (default false)● ANY DEFINED BY<identifier>

Optional


A

The StateChangeInfo type is defined in the file/opt/SUNWconn/em/etc/asn1/dmi.asn1

SNMP Trap NotificationsSolstice EM provides the following event notification types for mapping SNMPtraps:

• coldStartTrap• warmStartTrap• linkDownTrap

Table A-9 stateChange Event Notifications



Optional


stateChangeDefinition SET OF SEQUENCE of● attributeId● OptionaloldAttributeValue (ANYDEFINED BY<addtributeId>)● newAttributeValue(ANY DEFINED BY<attributeId>)

Required



Optional


additionalInformation SET OF SEQUENCE of● Object Identifier● BOOLEAN (defaultfalse)● ANY DEFINED BY<identifier>

Optional


A

• linkUpTrap• authenticationFailureTrap• egpNeighborLossTrap• enterpriseSpecificTrap

These notifications are defined in:/opt/SUNWconn/em/etc/gdmo/snmp_traps.gdmo.

SnmpTrapAlarmInfo is defined in:/opt/SUNWconn/em/etc/asn1/snmp_traps.asn1.

These event notifications have the structure described in Table A-10.

Table A-10 SNMP Trap Notification Attributes


probableCause CHOICE● globalValue (snmpTrapOID)● localValue (INTEGER)

Required

attributeIdList SET OF attributeIds derived fromcomponents of variable bindings

Optional

objectInstanceList SET OF Object Instancesassociated with variable bindings

Optional

unknownVarBindList CHOICE of● SEQUENCE of untranslatedSNMP v1 variable bindings● SEQUENCE of untranslatedSNMP v2 variable bindings

Optional

internetTrapInfo SET OF SEQUENCE of objectinstances, and attributes andvalues, in variable bindings

Optional


Optional

notificationId INTEGER Optional


A

correlatedNot SET OF SEQUENCE of correlatednotificationIds (INTEGER) andsource Object Instances

Optional

transportDomain Object Identifier for the transportprotocol associated with theagent that sent the alarm

Optional

transportAddress OCTET STRING containing thetransport layer address of theagent that issued the trap

Optional

accessControlInfo CHOICE of● communityString● partyInfo, which is aSEQUENCE of:— srcParty (Object Identifier)— dstParty (Object Identifer)— context (Object Identifier)

Optional

additionalInformation SET OF SEQUENCE● Object Identifier● BOOLEAN● ANY DEFINED BY <identifier>

additionalText GrasphicString Optional

Table A-10 SNMP Trap Notification Attributes


B-1

Environment Variables B

This appendix provides a table describing the environment variables used bySolstice EM and provides their default settings and a description of their use:

Table B-1 Environment Variables Used by Solstice EM

Environment Variable Name Default Setting Definition

System Environment Variables

DISPLAY localhost:0 Set to your local machine whendisplaying an application from aremote machine.

LD_LIBRARY_PATH /opt/SUNWconn/em/lib Shared object library path.

OPENWINHOME /usr/openwin Directory where Open Windowsis located.

PATH ./ Search path for executable files.

XFILESEARCHPATH /opt/SUNWconn/em/config/%N Search path for X files.

Solstice EM Environment Variables

EM_HOME /opt/SUNWconn/em Used by the applications toidentify where the SUNWemapppackage is installed.

EM_IMAGEDIR none Used as a pointer to where abackground image file is to befound.

B-2 Solstice Enterprise Manager Reference Manual

B

EM_MAPPATH $EM_HOME/mapdata Used by the Viewer to determinewhere vector map info is located.

EM_MIS_HOME /opt/SUNWconn/em Used by the MIS to identify wherethe SUNWemmis package isinstalled.

EM_RUNTIME /var/opt/SUNWconn/em Used by the MIS to identify wherethe runtime environment isinstalled.

EM_SERVER localhost Used by the applications toidentify the name of the machinewhere the MIS is running.

EM_MIS_PORT 5555 Used to specify the TCP/IP portnumber the MIS uses tocommunicate with applications.

EM_CMIP_MPA_DEFAULT_HOST localhost Used by the MIS to identify thename of the machine where thedefault CMIP MPA is located.

EM_CMIP_MPA_DEFAULT_PORT 5557 Used by the MIS to identify theport number used by the defaultCMIP MPA.

EM_MIS_DEFAULT_HOST localhost Used by the CMIP MPA toidentify the name of the machinewhere the MIS is located.

EM_MIS_DEFAULT_PORT 5557 Used by the CMIP MPA toidentify the port number the MISis using to communicate with it.

EM_HLOG_DIR /var/opt/SUNWconn/em/data/HLOG Specifies the default directorywhere historical log files are to bestored.

EM_HLOG_INTERVAL 0 Defines the rate (in hours) atwhich the historical log fileis created in EM_HLOG_DIR. 0 isthe default, meaning thathistorical log files are not created.



Environment Variables B-3

B

GRAPHER_PATHNAME /opt/SUNWconn/em/bin/em_grapher The path to the grapher forapplications that use the GrapherAPI.

Relational Database Environment Variables

ORACLE_HOME none Specifies the name of the Oraclehome directory.

ORACLE_SID none Specifies the Oracle system id.

ORACLE_TERM sun Specifies the terminal type.

SYBASE none Specifies the name of the homedirectory.



B-4 Solstice Enterprise Manager Reference Manual

B

C-1

Enterprise Manager File Structure C

This appendix provides a table describing the locations for components of theEnterprise Manager Product.

Table C-1 Summary of Default EM File Locations

Files Default Directory

Application configuration files /opt/SUNWconn/em/config

discover.conf file /opt/SUNWconn/em/config

Executables /opt/SUNWconn/em/config

Grapher API header files /opt/SUNWconn/em/include/grapher

Grapher API info /opt/SUNWconn/em/src/grapher

Header files /opt/SUNWconn/em/include

Help files /opt/SUNWconn/em/help

Icon files /opt/SUNWconn/em/glyphs

Runtime Libraries /opt/SUNWconn/em/lib

Sample agent and applicationsource code files

/opt/SUNWconn/em/src

snm.conf file /etc/opt/SUNWconn/snm

SunNet Manager managerservices libraries

/opt/SUNWconn/snm/lib

SunNet Manager agents /opt/SUNWconn/snm/agents

C-2 Solstice Enterprise Manager Reference Manual

C

SunNet Manager agents for Solaris2.x machines

/opt/SUNWconn/snm/5.x

MIS Machines Only:

ASN.1 definitions /opt/SUNWconn/em/etc/asn1

GDMO definitions /opt/SUNWconn/em/etc/gdmo

Compiled user ANS.1 definitions /var/opt/SUNWconn/em/data/ASN1

Compiled user GDMO definitions /var/opt/SUNWconn/em/data/MDR

Daemons /opt/SUNWconn/em/bin

Historical log files /var/opt/SUNWconn/em/data/HLOG

MIS configuration and startup files /var/opt/SUNWconn/em/conf

init_user file /var/opt/SUNWconn/em/conf

restart_user file /var/opt/SUNWconn/em/conf

SNMP MIBs /opt/SUNWconn/em/etc/snmp_mibs

Table C-1 Summary of Default EM File Locations

Files Default Directory

D-1

CMIS Scoping and Filtering D

Enterprise Manager supports CMIS filtering in the PMI and in the LogManager application. Section D.1, “OSI Definition of Scoping and Filtering”provides general background, while Section D.2, “Enterprise ManagerImplementation,” tells you how to use scoping and filtering in EnterpriseManager.

D.1 OSI Definition of Scoping and FilteringThe following figure and table illustrate the concepts of scoping and filtering.This information is taken from the OSI/Network Management Forum ApplicationServices document.

D-2 Solstice Enterprise Manager Reference Manual

D

Figure D-1 Scoping and Filtering: Hierarchy of Managed Objects

ObjectClass=root

AObjectClass=network

networkID=LEC AnetworkType=isdn

BObjectClass=network

networkID=LEC ZnetworkType=mobile

EObjectClass=equipment

equipmentID=NE1location=Birmingham

state=unlocked

FObjectClass=circuitcircuitID=NE1toNE2trafficVolume=0.75

state=locked

GObjectClass=equipment

equipmentID=NE2location=Atlantastate=locked

CObjectClass=circuitcircuitID=DS #1 464trafficVolume=0.72

state=unlocked

DObjectClass=service

serviceID=T1.5provider=LEC A

HObjectClass=circuit

circuitID=DS#22trafficVolume=0.33state=unlocked

IObjectClass=equipmentequipmentID=lineCard1

location=slot2state=unlocked

JObjectClass=equipmentequipmentID=lineCard2

location=slot3state=locked

KObjectClass=equipment

equipmentID=CPUlocation=slot22state=unlocked

CMIS Scoping and Filtering D-3

D

Table D-1 indicates the entries selected from Figure D-1 for a given base object,scope argument, and filter.

Table D-2 shows the ASN.1 notation for a filter, as defined in the ISO standardfor CMIP.

Table D-1 Scoped/Filtered Objects

Base Object Scope Argument Filter Scoped Entries Filtered Entries

B

baseObject networkType=mobile B B

oneLevelDown ((objectClass=equipment)& (state=unlocked)

E, F, G E

wholeSubTree ((objectClass=equipment)& (state=unlocked)

B, E, F, G, I, J, K E, I, K

root wholeSubTree (trafficVolume>.050) A-K C, F

Table D-2 ASN.1 Filter Notation

CMISFilter ::= CHOICE {

item [8] FilterItem,

and [9] IMPLICIT SET OF CMISFilter,

or [10] IMPLICIT SET OF CMISFilter,

not [11] CMISFilter

}

FilterItem ::= CHOICE {

equality [0] IMPLICIT Attribute,

substrings [1] IMPLICIT SEQUENCE OF CHOICE {

initialString [0] IMPLICIT SEQUENCE {

attributeId AttributeId,

string ANY DEFINED BY attributeId

},

anyString [1] IMPLICIT SEQUENCE {



D

Note that a filter consists of an assertion (FilterItem ) about the presence(present ) or values (equality , greaterOrEqual , lessOrEqual ,substrings, subsetOf, supersetOf, nonNullSetIntersection ) ofattributes in objects being tested. If a filter involves more than one assertion,the assertions can be grouped using and , or , and not . Filters can be arbitrarilycomplex, as you can nest filters within filters.

Within a discriminator construct, a single test is called an item. Within an item,a relationship is written with the comparison operator preceding a pair of curlybraces, which enclose an operand. The following is the general form:

string ANY DEFINED BY attributeId

},

finalString [2] IMPLICIT SEQUENCE {


string ANY DEFINED BY attributeId}

},

greaterOrEqual [2] IMPLICIT Attribute,

-- asserted value >= attribute value

lessOrEqual [3] IMPLICIT Attribute,

-- asserted value <= attribute value

present [4] AttributeId,

subsetOf [5] IMPLICIT Attribute,

-- asserted value is a subset of attribute value

supersetOf [6] IMPLICIT Attribute,

-- asserted value is a superset of attribute value

nonNullSetIntersection [7] IMPLICIT Attribute

}

item : <operator> : { <operand> }

Table D-2 ASN.1 Filter Notation


D

The term item is one of four keywords that can be used to specify the formatof a CMIS filter. These format specifiers can be item , and , or , or not .Table D-3 defines these terms.

The <operator> in the preceding example is the “verb” in a given filter item.Table D-4 defines the operators.

The <operand> is, in GDMO terms, an Attribute, which by definition, is a name-value pair. So, we can further refine the general form as:

Table D-3 Format Specifier Definitions

Name Descriptions

item A single FilterItem, which is a choice of a test for equality, less than or equal, greater than orequal, substring matching, or presence in. These filter “verbs” are described in Table D-4.

and The logical ANDing of a set of CMIS filters.

or The logical ORing of a set of CMIS filters.

not The negation of the sense of one CMIS filter.

Table D-4 Operator Definitions

Name Description

equality Is the item we are filtering equal to this operand?

substrings This breaks down to the operators initialstring , anystring , and finalstring .Is the string under consideration match the beginning, end, or any part of the string inthe operand?

greaterOrEqual Is the item we are filtering greater than or equal to this operand?

lessOrEqual Is the item we are filtering less than or equal to this operand?

present Is the item we are filtering present in the operand?

subsetOf Are all asserted members present in the attribute?

supersetOf Are all members of the attribute present in the asserted attribute?

nonNullSetIntersection Is at least 1 asserted member present in the attribute?

item : <operator> : { <name_string>, <value_string> }


D

Using the and and or format specifier, you can build nested filters. These areof the form:

D.2 Enterprise Manager ImplementationEnterprise Manager supports scoping and filtering of object instances in thefollowing areas:

• In the Log Manager, in the discriminator construct

• When deriving Album instances in the high-level use of the PortableManagement Interface (PMI)

D.2.1 Log Manager Discriminator Construct

In the Log Manager, a discriminator construct is an expression used to decidewhich event notification types will be accepted by a particular log object. Youuse the following syntax:

For simple, non-nested filters, the <format specifier> is item . The precedingsyntax can be further refined as:

and (or or ){item : <operator> : { <name_stringA>, <value_stringA> },item : <operator> : { <name_stringB>, <value_stringB> }}

<format specifier> : <operator> : { <operand> }

item : [ <relationship>] : { <attribute name>, <attribute value> }


D

Below is the default Log Manager discriminator construct. In this example, theattribute name is on the second line and the attribute value is on the third line.Together, they form a single attribute against which an event notification willbe tested for equality.

D.2.2 Filtering as an Aspect of Album Derivation

The Album function set_derivation() (or its more general form set_prop )can specify a derivation that includes a CMIS filter. The derivation specifiesthree items, in this order:

1. Object name

2. Scope

3. Filter

A slash separates the scope from the object name. If there is a filter, a slashseparates the scope from the filter.

The following is an example of filtering using the PMI:

The result of the previous example is that one object is added to an Album . Thepreceding example is equivalent to:

item : equality : {attributeId globalForm : “Rec. X.721 | ISO/IEC 10165-2 : 1992”:eventType,attributeValue globalForm : “iimcManagementDoc 1”:internetAlarm

}

CMISFilter(“and: { item: equality: {objectClass, topoType}, item: equality: {topoTypeId,

‘Network’} }”)

(objectClass == topoType) && (topoTypeId == Network)


D

D.2.2.1 Object Name

An object name is a distinguished name in slash form. The object namespecifies the base object for scoping. This base object is not necessarily one ofthe objects in the album.

It is permissible to omit the object name. If you omit the object name, thesystem object is assumed. Note that if you omit the object name, you shouldnot insert the slash that would separate the name from the derivation. If youwrite /ALL , you are indicating an object name of / (indicating the systemobject), followed by the scope ALL.

D.2.2.2 Scope

The scope can be any of the following:

If omitted, the scope defaults to the base object only. Note that the asteriskforms are short for LV(n), not TO(n).

D.2.2.3 Filter

The filter is currently specified in raw ASN.1 format. The definition of the filtergoes inside the parentheses that follow CMISFilter . This syntax makesCMISFilter look like a function. In fact, it is not a function; the use ofparentheses is simply a convention for delimiting the filter definition.

Table D-5 Scoping Parameters

Parameter Description

ALL All descendants of named object, including object.

LV (<n>) Level <n> descendants only. Children are at LV(1).Grandchildren are at LV(2). The base object is at LV(0).

TO (<n>) All levels down to level <n>, including object

* Short for LV(1), i.e. children only

*/* Short for LV(2), i.e. grandchildren only.

*/*/* Short for LV(3), i.e. great-grandchildren only.


D

Omitting the filter has the same effect as a filter whose definition is TRUE,meaning “include everything specified by the scope”. The definition of a legalCMISFilter is specified in etc/asn1/x711.asn1 , which is a formalizationof the X.711 standard.

As an example of filtering, to find all of the OMNIPoint logs under the systemobject, any of the expressions shown below would be a valid argument toAlbum::set_derivation() .

Building on the previous examples, to get only logs that are enabled, filter onoperationState, using and, as shown below:

For the PMI, new lines are allowed and might enhance readability. Note thatnew lines might not be accepted by a shell.

D.2.2.4 Operation of a Filtering Derivation

When a filtered Album is derived, the filtering is done automatically by theplatform, so you never see any callbacks for the objects that are bypassed bythe filter. If the Album ’s TRACKMODE is set to TRACK, the Album ismaintained on the basis of the filter. That is, if an attribute changes in a waythat makes the value of the filter true (when it has been false) or false (when ithas been true), the Album is automatically updated so that the Image of theobject is included (or excluded, as appropriate).

If the Album is not set to TRACK, you can perform another scoped and filteredM-GET by calling derive() again.

/systemId=”mysys”/LV(1)/CMISFilter(item:equality:{objectClass,log}) orLV(1)/CMISFilter(item: equality: {objectClass, log}) or*/CMISFilter(item:equality:{objectClass,log})

LV(1)/CMISFilter( and: { item: equality: {objectClass, log}, item: equality: {operationState, enabled})


D

If you execute all_destroy() on an Album that has a derivation and thatAlbum is in a DOWN state, or is an AUTOIMAGE Album, then the request isoptimized to do a single scoped M-DELETE using the scope and filter specifiedfor the Album . (Otherwise a separate M-DELETE is issued for each member ofthe Album , as before.)

The other ALL operations are not yet optimized in this way, but you can get theeffect of an optimized all_boot() : If you execute derive() on anAUTOIMAGE Album, the initial scoped M-GET fetches all the attributes at thattime, rather than issuing a subsequent M-GET for each Image.

E-1

Additional Sources of Information E

Listed here are the documents relating to network management from thevarious standards bodies referred to throughout the Solstice EnterpriseManager product documentation. The documents are categorized by theirtopics. To complete tasks in the Solstice Enterprise Manager ApplicationDevelopment Guide, see ✔ items.

E.1 Network Management Concepts• ITU X.200 – Reference model of open systems interconnection for ITU

applications, 1988

• ISO/IEC 7498, Information processing systems – Open SystemsInterconnection – Basic reference model, 1984

• ITU X.700 ISO/IEC 7498-4, Information Processing Systems – Open SystemsInterconnection – Basic Reference Model – Part 4: Management framework

• ITU X.701 ISO/IEC 10040, Information Technology – Systems ManagementOverview

• RFC-1411, Introduction to Version 2 of the Internet-standard NetworkManagement Framework

• ITU X.700 series – Management framework definition for Open SystemsInterconnection (OSI) for ITU applications

✔

✔

E-2 Solstice Enterprise Manager Reference Manual

E

• Discovering OMNIPoint. A common approach to the integratedmanagement of network information systems. Network ManagementForum. Prentice Hall, 1993.

• Jock Embry, Peter Manson, Dave Milham. Interoperable NetworkManagement: OSI/NM Forum architecture and concepts. In IntegratedNetwork Management II, I. Krishnan and W. Zimmer (eds.), Elsevier SciencePublishers BV, North-Holland. 1991, pp. 29–44. (Partly overlaps content ofthe Forum Architecture document).

• Forum Architecture. Forum 004, issue 1.0, January 1990. OSI/NetworkManagement Forum, Bernardsville, N.J. (Partly overlaps content of theEmbry, Manson, and Milham article).

E.2 ISO Network Management Concepts

E.2.1 General Concepts• ITU X.720 ISO/IEC 10165-1, Information Technology – Open Systems

Interconnection – Structure of Management Information – Part 1:Management Information Model

• ITU X.734 ISO/IEC 10164-5, Information Technology – Open SystemsInterconnection – Systems Management – Part 5: Event Report ManagementFunction

• ITU X.735 ISO/IEC 10164-6, Information Technology – Open SystemsInterconnection – Systems Management – Part 6: Log Control Function

• ITU X.730 ISO/IEC 10164-1, Information Technology – Open SystemsInterconnection – Systems Management – Part 1: Object ManagementFunction

• ITU X.731 ISO/IEC 10164-2, Information Technology – Open SystemsInterconnection – Systems Management – Part 2: State ManagementFunction

• ITU X.732 ISO/IEC 10164-3, Information Technology – Open SystemsInterconnection – Systems Management – Part 3: Attributes for RepresentingRelationships

✔

✔

✔

Additional Sources of Information E-3

E

• ITU X.733 ISO/IEC 10164-4, Information Technology – Open SystemsInterconnection – Systems Management – Part 4: Alarm Reporting Function

E.2.2 Abstract Syntax Notation One (ASN.1)• ITU X.208 ISO/IEC 8824, Specification of Abstract Syntax Notation One

(ASN.1)

• ITU X.209 ISO/IEC 8825, Specification of Basic Encoding Rules for AbstractSyntax Notation One (ASN.1)

E.2.3 CMIP• ITU X.710 ISO/IEC 9595, Common Management Information Service

Definition

• ITU X.711 ISO/IEC 9596-1, Common Management Information ProtocolSpecification1

E.2.4 CMIP over TCP/IP• RFC 1189, CMOT: CMIP over TCP/IP

E.2.5 GDMO• ITU X.721 ISO/IEC 10165-2, Information Technology – Open Systems

Interconnection – Structure of Management Information – Part 2: Definitionof Management Information

• ITU X.722 ISO/IEC 10165-4, Information Technology – Open SystemsInterconnection – Structure of Management Information – Part 4: Guidelinesfor the Definition of Managed Objects (GDMO)

1. This is CMIP version 2. CMIP version 1 was described in ISO/IEC 9596 and has no corresponding ITUspecification.

✔

✔

✔

✔

✔

✔


E

E.2.6 ACSE• ITU X.217, ISO/IEC 8649, Information processing systems – Open Systems

Interconnection – Common Management Information Protocol – ServiceDefinition for the Association Control Service Element

• ITU X.227, ISO/IEC 8650, Information processing systems – Open SystemsInterconnection – Common Management Information Protocol – Protocolspecification for the Association Control Service Element, 1988

E.2.7 ROSE• ITU X.219, Remote Operations: Model, Notation, and Service Definitions,

1988

• ITU X.229, Remote Operations: Protocol Specification, 1988

E.2.8 Directory Model• ITU X.500, Information Technology – Open Systems Interconnection – The

directory: Overview of Concepts, Models, and Services, 1993

• ISO/IEC 9594-2, Information Technology – Open Systems Interconnection –The directory – Part 2: Models, 1988

E.2.9 CMIS• ITU X.710, Common Management Information Service definition for ITU

applications, 1991

• ISO/IEC 9595, Information Technology – Open Systems Interconnection –Common Management Information Service definition, 1991

E.2.10 Management Information Model• ITU X.720. ISO/IEC 10165-1, Information Technology – Open Systems

Interconnection – Structure of Management Information – Part 1:Management information model

• ITU X.721. ISO/10165-2, Information Technology – Open SystemsInterconnection – Structure of Management Information – Part 2: Definitionof management information, 1992


E

E.2.11 System Management• ITU X.730 | ISO 10164-1 Information Technology – Open Systems

Interconnection – Object Management Function

• ITU X.731 | ISO 10164-2 Information Technology – Open SystemsInterconnection – State Management Function

• ITU X.732 | ISO 10164-3 Information Technology – Open SystemsInterconnection – Attributes for Representing Relationships

• ITU X.733 | ISO 10164-4 Information Technology – Open SystemsInterconnection – Alarm Management Function

• ITU X.734 | ISO 10164-5 Information Technology – Open SystemsInterconnection – Event Management Function

• ITU X.735. ISO/IEC 10164-6. Information Technology – Open SystemsInterconnection – Log Control Function

• ITU X.736 | ISO 10164-7 Information Technology – Open SystemsInterconnection – Security Alarm Reporting Function

• ITU X.740 | ISO 10164-8 Information Technology – Open SystemsInterconnection – Security Audit Trail Function

• ISO 10164-9 Information Technology – Open Systems Interconnection –Objects and Attributes for Access Control

• ISO 10164-10 Information Technology – Open Systems Interconnection –Usage metering function

• ISO 10164-11 Information Technology – Open Systems Interconnection –Metric Objects and attributes

• ISO 10164-12 Information Technology – Open Systems Interconnection – TestManagement Function

• ISO 10164-13 Information Technology – Open Systems Interconnection –Summarization Function

• ISO 10164-14 Information Technology – Open Systems Interconnection –Confidence and Diagnostic Test categories

• ISO 10164-15 Information Technology – Open Systems Interconnection –Scheduling Function


E

E.2.12 Logging• Network Management Forum: Forum 006, Forum Library – Volume 4:

OMNIPoint 1 Definitions, 1992

• Network Management Forum: Forum 019, OMNIPoint 1 Object andEnsemble List, 1992

E.2.13 Profiles

Profiles have been defined in the area of OSI Management in order to facilitatethe use of standards, especially by procurement. At the moment the followingprofiles are published ISPs or ISPs awaiting publication:

• AOM1x profiles specify the use of OSI upper layers (Session, Presentation,ACSE, ROSE) and CMIP, over a connection oriented Transport service. Theyprovide Management communications capability.

• Both AOM11 (Basic Management Communications) and AOM12 (EnhancedManagement Communications) require the conforming implementations tosupport all of he CMIS service primitives in the MIS functional unit in bothmanager and agent roles. AOM12 requires in addition the support ofMultiple Object Selection, Filter, Multiple reply, and Cancel-get.

• AOM2x profiles specify the use of OSI system management functions.

• AOM211 (General Management Capabilities) provides system managementfunction support for general operations on Managed objects, including theability to create, delete any managed object, retrieve and modify anyattribute, report any event, and initiate any action.

• AOM212 (Alarm reporting and state management capabilities) and AOM213(Alarm Reporting Capabilities) are subsets of AOM211 and provide only forthe reporting of alarms (AOM213), and the reporting of state attributechange and alarms (AOM212).

• AOM221 (General Event Report Management) provides the ability to selectwhich notifications will be transmitted externally, and where they will besent.

• AOM231 (General Log Control) provides the ability to select whichnotifications or incoming event reports will be logged and their subsequentretrieval.


E

E.3 Telecommunication Management Network(TMN) Standards

The Solstice EM architecture seeks to conform to the following TMN standards:

• ISO/ITU M.3010, Maintenance: Telecommunications Network. Principles fora Telecommunications Management Network, October 1992

• ISO/ITU M.3020, Maintenance: Telecommunications Network. TMNInterface Specification Methodology, October 1992

• ISO/ITU M.3180, Maintenance: Telecommunications Network. Catalogue ofTMN Management Information, October 1992

E.4 Internet Network Management Concepts

E.4.1 SNMP• RFC 1351, SNMP Administrative Model, 1992

• RFC1352, SNMP Security Protocols, 1992

• RFC 1353, Secure SNMP - Release 2.0

E.4.2 SNMP Version 1• RFC 1155, Structure and Identification of Management Information for

TCP/IP-based Internets

• RFC 1157, A Simple Network Management Protocol (SNMP Version 1)

• RFC 1212, Concise MIB Definitions

• RFC 1213, Management Information Base for Network Management ofTCP/IP-based Internets: MIB-II

• RFC 1215, A Convention for Defining Traps for use with SNMP

E.4.3 SNMP Version 2• RFC 1442,Structure of Management Information for version 2 of the Simple

Network Management Protocol

✔

✔

✔

✔

✔

✔


E

• RFC 1445, Introduction to version 2 of the Internet-standard NetworkManagement Framework

• RFC 1448,Protocol Operations for version 2 of the Simple NetworkManagement Protocol (SNMPv2)

• RFC 1445, Administrative Model for version 2 of the Simple NetworkManagement Protocol

• RFC 1446, Security Protocols for version 2 of the Simple NetworkManagement Protocol

E.4.4 ISO and Internet Management Co-existence

The ISO and Internet Management Co-existence specifications are availableboth as Network Management Forum specifications and also asanonymous ftp sites from:

thumper.bellcore.com (128.96.41.1)

The documents can be found in the following directory:

pub/forum/iimc/issue1

The Forum specifications are:

• Forum 026, Translation of Internet MIBs to ISO/CCITT GDMO MIBs, Issue1.0, 1993

• Forum 027, ISO/CCITT to Internet Management Security, Issue 1.0, 1993

• Forum 028, ISO/CCITT to Internet Management Proxy, Issue 1.0, 1993

• Forum 029, Translation of Internet MIB-II to ISO/CCITT GDMO MIB, Issue1.0, 1993

• ISO/ITU and Internet Management Coexistence (IIMC): Translation ofISO/ITU GDMO MIBs to Internet MIBs (IIMCOMIBTRANS Internet DraftMay 26, 1993, work in progress)

• ISO/ITU and Internet Management Coexistence (IIMC): Translation ofInternet MIBs to ISO/ITU GDMO MIBs (IIMCIMIBTRANS Internet DraftAugust 5, 1993, work in progress)

• ISO/ITU and Internet Management Coexistence (IIMC): Translation ofInternet MIB-II (RFC 1213) to ISO/ITU GDMO MIB (IIMCMIB-II InternetDraft August 5, 1993, work in progress)

✔

✔

✔

✔

✔

✔


E

• ISO/ITU and Internet Management Coexistence (IIMC): ISO/ITU to InternetManagement Proxy (IIMCPROXY Internet Draft May 26, 1993, work inprogress)

• ISO/ITU and Internet Management Coexistence (IIMC): ISO/ITU to InternetManagement Security (IIMCSEC Internet Draft August 3, 1993, work inprogress)

• RFC-1214 OSI Internet Management: Management Information Base

• ISO/ITU SMI Guidelines for Definition of Managed Objects [ISO10165-4]

E.4.5 MIB I• RFC 1156 MIB I

• RFC 1212 Concise MIB definitions. M.T. Rose & K. McCloughrie, 1991

E.4.6 MIB II• RFC 1158 MIB II

• RFC 1213 Management Information Base for TCP/IP-based networks. M.T.Rose & K. McCloughrie, 1991

E.4.7 Host Resources MIB• RFC 1514. Host Resources MIB, P. Grillo & S. Waldbusser, 1993

This memo defines a MIB for use with managing host systems. The term“host” is construed to mean any computer that communicates with othersimilar computers attached to the internet and that is directly used by oneor more human beings. Although this MIB does not necessarily apply todevices whose primary function is communications services (e.g., terminalservers, routers, bridges, monitoring equipment), such relevance is notexplicitly precluded. This MIB instruments attributes common to all internethosts including, for example, both personal computers and systems that runvariants of Unix. This memo is a product of the Host Resources MIBWorking Group of the IETF.


E

E.5 Application-to-Application Communication• The Common Object Request Broker: Architecture and Specification, OMG

Document Number 91.12.1 Revision 1.1

E.6 Additional InformationThe following book is considered a classic in the field of network management.It contains a good introduction and description of Internet networkmanagement:

• Rose, Marshall T., The Simple Book: An Introduction to Management ofTCP/IP-based Internets, Prentice-Hall, second edition, 1994.

In addition to the above book, you may also find the following book to beuseful:

• Rose, Marshall T., The Open Book: A Practical Perspective on OSI, Prentice-Hall., 1989.

E.7 Where to Find These Reference Materials

E.7.1 ISO Specifications

You can obtain ISO specifications from the following organization:

Phillips Business Information1201 Seven Locks RoadPotomac, MD 20854800-777-5006703-281-1135

You can get ANSI specs from ANSI, as follows:

ANSI11 W. 42nd StreetNew York, NY 10036Attn.: Sales Department212-642-4900


E

E.7.2 Internet RFCs

Internet RFCs are available by anonymous ftp from several ftp sites. Some common ftpsites for RFCs are:

U.S. Address:

ds.internic.net (198.49.45.10)

Pacific Rim Address:

munnari.oz.au (128.250.1.21)

Europe Address:

nic.nordu.net (192.36.148.17)

E.7.3 OMNIPoint Specifications

The OMNIPoint specification was developed by the Network ManagementForum. The OMNIPoint specification provides a comprehensive description ofISO network management in a much more readable form than the ISOstandards documents. OMNIPoint also includes a number of specificationsdescribing ISO and Internet co-existence and internetworking strategies. Partof the co-existence description defines a mechanism for managing Internet(SNMP) devices from an ISO (CMIP) management platform. The co-existencestrategy described by OMNIPoint is based on the CMIP-SNMP co-existenceimplementation developed for Solstice EM. Although, the Solstice EMimplementation pre-dates the final OMNIPoint specification. The OMNIPointspecifications can be obtained from the Network Management Forum. You cancontact the Network Management Forum as follows:

Contact: Document SalesNetwork Management Forum1201 Mt. Kemble AvenueMorristown, NJ 07960-6628 USA201-425-1900201-425-1515 (fax)


E

Glossary–1

Glossary

This glossary offers brief descriptions of terms that appear in the discussion ofthe Solstice EM system, either because they are used in the industry or becausethey have specific meanings in the Solstice EM context.

This glossary contains the following types of terms:

• Those specific to OSI management and OMNIPoint 1

• Those specific to the SNMP environment

• Those specific to the CMIP environment

• Those with definitions common to SNMP and CMIP environments

• Those with definitions different for SNMP and CMIP environments

Definitions specific to the SNMP environment and SNMP terms that have adifferent meaning in CMIP are indicated by [S]. Definitions specific to theCMIP environment and CMIP terms that have a different meaning in SNMPare indicated by [C]. Definitions common to both environments have noindicator.

Terms in italics are defined within this glossary.

ACSEAssociation Control Service Element. ACSE is a generic grouping of the serviceelements within the application layer that together offer services related to theestablishment and management of a cooperative relationship between peerapplication processes.

Glossary-2 Solstice Enterprise Manager Reference Manual

actionIn the Request Designer service, the response that a request manager makeswhen a transition occurs. In a request template, the definition of a transition liststhe actions (if any) to take when a transition occurs. The actions are selectedfrom a small set of supported actions. However, each action takes an argumentthat gives it great latitude in specifying details of the action, particularly whenthe action is a condition.

agentAlso called Network Management Agent. A module residing in a managedresource on a network, capable of reporting the status of the resource and/orresponding to inquiries about it. Described in standards documents X.701 |ISO/IEC 10040.In a general sense, software running on a managed object that responds to andreports to the Solstice EM MIS with current information about the object.See also Proxy Agent.

APIApplication Programming Interface. An API is a set of software routines thatenables an applications developer to access and use the features of a product.In Solstice EM, the API is called the Portable Management Interface (PMI).

ARPAddress Resolution Protocol. A procedure for finding the network hardwareaddress corresponding to an internet address (RFC 826).

ASN.1Abstract Syntax Notation One. A specification understood by networkmanagement protocols and used for encoding information between a managerand agents in a machine- and network-independent manner.

ASN.1 compilerAn Solstice EM program (em_asn1) that accepts ASN.1 descriptions forultimate inclusion in the MetaData Repository (MDR) of a running Solstice EMMIS.

attachment instanceAn object class instance of a line attachment to a node. See class instance.You can attach each end of a Viewer application line icon to a node. Theattachment has two aspects: it is a graphical representation of one portion ofthe physical network; it is an object class on the node (such as an object forport or connection information).

Glossary-3

attributeAn attribute is an item of management information that describes someproperty of a managed object—its operational characteristics, conditions ofoperation, or current state or status. In the SNMP world, also called a Non-Aggregate Object. In the context of Solstice EM, an object type in an MIT orMIB module that is part of an object class (a child of the object class). Anattribute has identification and a value. Instances of managed objectsbelonging to the same class have the same set of attributes with the same set ofidentifications; only the values of the attributes can differ from one instance toanother.See also object class and class instance.

authentication entityThat portion of an SNMP agent responsible for verifying that an SNMP entityis a member of the community it claims to be in. The authentication entity isalso responsible for encoding and decoding SNMP messages according to theauthentication algorithm of a given community. This entity is used in securityalarms.

AV pairAttribute-Value pair.

AVAAttribute Value Assertion. An assertion that a particular attribute has aparticular value.See also RDN

base objectSee object class.

base-object instanceSee class instance.

BSSBacking Storage System. A set of methods included in an API to enable managedobjects to be written to and read from a database.

callbackThe object (or method) to be notified at completion of an asynchronousprocess. Typically, when a client process requests something from an MIS, therequest includes a pointer to the function to be invoked when the MIS is ready.


childA subordinate object contained in an instance of a class and directly below thatclass instance. [C]

classIn general, the formal description of a set of objects. In the OSI world, objectswith similar attributes and behavior are grouped into classes. In C++, the rulesgoverning a set of data structures (which are said to be instances of the class)and the methods (also called member functions) which give access to aninstance’s data.

class instanceA collection of attribute instance values that specifies one example of a class.For example, if the class comprised port information for a router port, youcould specify an instance of the class by providing a router board and portnumber for a particular port. The information you provide to specify a classinstance is called the instance identifier. Other related terms are instance string,Relative Distinguished Name (RDN), Index, and Named Object.

CLNSConnection-Less Network Service. A network service provided at Layer 3 ofthe OSI protocol stack.

CM-APISee XMP.

CMEConformant Management Entity. Any management system that supports theinteroperable interface defined by the Network Management Forum (of whichthe Solstice EM MIS is one).

CMIPCommon Management Information Protocol. CMIP is the protocol specified aspart of CMIS; part of the OSI protocol stack. CMIP is a connection-orientedprotocol, with reliable delivery. It is the same as Recommendation X.711, asdefined by the ITU (International Telecommunications Union). CMIP wasdeveloped to support distributed management appropriate to complex wide-area networks as well as local-area networks. It is object-oriented, and oftenused with a programming agent between a device and management system.

Glossary-5

CMIP MPACMIP Management Protocol Adaptor. An Solstice EM component that allowsaccess to OSI managed resources via CMIP. The CMIP MPA receivesmanagement directives from the Management Information Server (MIS) andtranslates the directives into CMIP messages. The CMIP MPA also receivesnotifications from OSI managed objects and sends them to the MIS.

CMISCommon Management Information Services. An ISO standard that defines theservices required of systems that exchange network management information,such as requests to supply the values of attributes or to send reports of events.Management services as defined by the ITU Recommendation X.710.

CMOTCommon Management Information Protocol Over TCP/IP. CMIP for theTCP/IP environment.

community stringAn SNMP concept. A simple password that you provide when adding a nodeicon to the network view. The agent running on the node requires thispassword from Solstice EM before providing information about the node. [S]

compilerGenerally, a process that analyzes a statement into its syntactic components.Specifically, Solstice EM provides compilers that process the descriptions ofmanaged object classes written according to the GDMO specifications(em_gdmo), according to ASN.1 specifications (em_asn1), and descriptions ofmanaged object classes written in Internet MIB format (em_cmib2gdmo).Output of these compilers supply the internal formats needed for the MDR andthe ASN.1 repository.

Concise MIBIn the SNMP world, an extensible system for classifying information aboutmanaged objects in a network. Specifically, a particular extension offered bythe manufacturer of a device in order to accommodate information about thatdevice within the general MIB (Management Information Base) structure. SeeRFCs 1156 and 1213, which define, respectively, MIB-I and MIB-II, which arethe MIBs for TCP/IP-based internetworks. (See also MIB.)

Concise MIB compilerAn Solstice EM program (em_cmib2gdmo) that accepts the description of anInternet MIB (Management Information Base) and generates paralleldescriptions in GDMO (which may then be submitted to the GDMO compiler


(em_gdmo)) and ASN.1 (which may then be submitted to the ASN.1 compiler(em_asn1)) for ultimate inclusion in the Management Information Tree (MIT)and MetaData Repository (MDR) of a running Solstice EM MIS.

conditionA term used in Solstice EM requests. A set of instructions written in the RequestCondition Language (RCL). A condition serves two functions in requests:

• Its primary function is to test whether a request for a specific set (one ormore) of managed objects will cause a transition from one state to another (orloop back to the same state). You must have at least one condition associatedwith each transition. Where there are multiple conditions, the requestfacilities evaluate conditions in the order they are entered in the requesttemplate.

• A second function of a condition is as an action, taken in response to atransition. A condition is one of three alternatives you have for actions.

When used to test whether to make a transition, the value of the condition(true is nonzero, false is zero) is the value returned by the last statement in thecondition. When used as an action, the value returned by the condition is notused by the request facilities.

container iconIn the Viewer, an icon that can contain other icons, or more precisely, an iconrepresenting a managed object that can contain other managed objects.Examples of such icons are networks and subnetworks. A container icon isequivalent to a view and is distinguished from an element or a link icon.

CORBACommon Object Request Broker Architecture. Structure for interchange ofobjects in a network management environment. Developed by OMG.

COSECommon Open Software Environment. Common network system managementenvironment proposed by IBM, HP, Sun, and Unix Systems Labs. Rival to DMEfrom OSF.

DBMDataBase Manager. A simple database manager (for example, that used by theSolstice EM backing store) that is useful where a more powerful relationaldatabase package is not needed.

Glossary-7

deviceA network element of some kind. In the Solstice EM documentation, refers tobridges, routers, and other network nodes that are not hosts (that is, thatcannot accept logins).

DiscoverAn Solstice EM application that locates manageable objects and adds them tothe MIS. Refer to Chapter 11, “Discover,” for detailed information.

discriminator constructThe proposition that a log object tests in order to decide whether to keep arecord of a notification. Each log object has exactly one discriminator construct.The discriminator construct is an expression that can be evaluated for theattributes contained in the notification message. A discriminator construct iswritten in the language prescribed for a CMIS filter, as specified in ISO/IEC9595. A discriminator construct is also used by the Event ForwardingDiscriminator to determine whether a received notification needs to beforwarded to an application.

distinguished nameA name that identifies a position within the Management Information Tree(MIT). A name may be a Fully Distinguished Name (FDN) and include thecomplete path from the root of the tree, a Relative Distinguished Name (RDN)with respect to a current position in the tree, or a Local Distinguished Name(LDN).

DMEDistributed Management Environment. Network management environment ofthe OSF.

DMIDefinition of Managed Information.

EFDEvent Forwarding Discriminator. In OMNIPoint 1 terminology (and in SolsticeEM), an object that decides whether and where to forward a notificationreceived from a managed object. Conceptually equivalent to a sieve.

elementSometimes referred to as network element. In OMNIPoint terminology, acomponent or device to be managed (that is, part of a managed resource). InGUI terminology, a graphical component of the user interface (for example, aline, rectangle, ellipse, etc.).


Element libraryCollection of C++ classes that extend the Solstice EM GUI API to permitmanipulation of graphic elements within the display.

environment variableA variable set in the UNIX shell environment to which an application maymake reference. For example, used to specify the Solstice EM MIS to which anSolstice EM service connects.

eventA notification to which a software system must respond when it occurs butwhich it did not solicit or control. In network management, a notification of astatus change that arises externally, rather than being solicited by the manager.In CMIP usage, an event is a report that is automatically sent from a nodeagent. In SNMP, this is referred to as a trap.

FDNFully Distinguished Name. In the Management Information Tree (MIT), thecomplete path to a managed object instance. See also RDN and Name.

filterThe use of a Boolean expression to test a set of attributes in order to select theobjects to which a network management command is addressed. Objectinstances that successfully pass the filtering tests become those on which amanagement operation is performed. Defined by the CMIS specification(ISO/IEC 9595), CMIP filtering capabilities help reduce the network trafficoverhead of a management protocol. See also scoping.This usage of “filter” is distinct from the usage in UNIX systems, where a filteris a program that accepts input from one stream and supplies output inanother, so that it can be piped to other functions as needed.

FIPSFederal Information Processing Standards. Summary of standards forcomputer and communication systems developed by US National Institute ofStandards and Technology. Includes GNMP.

ForumSee Network Management Forum.

gatewayA computer that interconnect two networks and routes packets from one to theother. A gateway has more than one network interface.

Glossary-9

GDMOGuidelines for the Definition of Managed Objects. An ISO document (ISO/IEC10165-1 and ITU Recommendation X.722) that describes a formal specificationlanguage used to define the MIT object class syntax, and consequently, theform in which managed objects are defined for client services.

GDMO compilerA Solstice EM utility (em_gdmo) that parses a description written in GDMOformat and compiles it for inclusion in the MetaData Repository.

GNMPGovernment Network Management Profile. A US government checklist offeatures of a network management system. See also FIPS.

GOSIPGovernment OSI Profile. Standards and recommendations for government useof computers and communications. Separate U.S. and U.K. GOSIP standardsexist, but cover the same general topics.

ground stateIn the Request Designer, the state that a request is in when it is first created; thefirst state in a request template. The sole requirement for this state is that ithave a severity of normal.

GUIGraphical User Interface. Solstice EM makes use of the Motif Window Managerto generate application interfaces using the Motif library of interface routines.

hopThe traversing of a router. The hop count is a metric for distance used in IProuting. Used in the Discover application to delimit the extent of Discover’ssearch.

hostA host is any network node that can accept logins. In Internet terminology, ahost is an end-system. However, in the Solstice EM screen interface, a host isany node in the network that is running an SNMP or CMOT agent (such as aworkstation, bridge, router, terminal concentrator, or switch).

ICMPInternet Control Message Protocol. The protocol that specifies error and controlmessages used with the Internet protocols.


indexSee class instance.

IABInternet Activities Board.

IETFInternet Engineering Task Force. Source of MIB, SNMP.

instanceIn C++, a piece of data whose structure is described by its membership in aclass. Access to the data is provided only by the member functions defined bythe class. For managed objects, a specific case or example of a managed object.For example, routers might be taken as an object class; one particular routerwould be an instance of that class.

instance identifierIn the OSI world, the fully distinguished name of an instance in a ManagementInformation Tree (MIT). The instance identifier is unique within a givensystem.In SNMP, the values for the attributes of a base object take the form of a table:attributes define the columns, and class instances define the rows. The instanceidentifier comprises the elements in a row that uniquely identify that row.Some base objects in vendor MIBs are extensions of base objects in standardMIBs. For such a base object, the instance identifier might be found in theoriginal base object, not the extension.

instance specifierSee instance identifier.

InternetA large collection of connected networks, primarily in the United States,running the Internet suite of protocols. The generic term “internet” refers to acollection of TCP/IP internetworks.

interoperabilityThe capability of two or more systems to meet user requirements bycommunicating through specific mechanisms in a known environment.

IP addressA 32-bit quantity used to represent a point of attachment in a TCP/IP-basedInternet.

Glossary-11

ISOInternational Standards Organization. Develops standards, by internationalagreement, over a wide range of technical areas.

log objectAn object that contains several attributes used to test incoming events. If anevent occurs, and passes all the Log Object tests, a record (Log Record) of theevent is stored in the system. The tests consist of a discriminator (test againstthe attributes of the event), and a test against a specified size (if the size of thelog records, in octets, is greater than the allowable size, the new record is notcreated).

log recordan object that contains the attributes for an event which passed the tests of theLog Object.

major trap numberThe SNMP standard RFC1157 defines seven categories of traps, numbered 0through 6. These numbers are called the major trap numbers.

managed lineAny line, created as an Solstice EM line icon, with manageable lineattachments.

managed nodeA network computer, router, hub, or other piece of equipment on the networkthat has object classes entered in the Solstice EM MIT and a network agentrunning on it.

managed objectThe representation of a network resource (or a set of resources). Note that ingeneral a managed object is an abstraction that represents selected attributes ofthe resource it represents. The managed object resides within the MIS, where itrepresents a resource that is elsewhere. A managed object is characterized by:

• attributes visible at its boundary• management operations that may be applied to it• behaviors it exhibits in response to management operations


• notifications that it emitsA MIB or MIT entry that represents some aspect of a network node or line thatcan be monitored and, in some cases, set, using Solstice EM services. The MISmanages the object by polling it, displaying the attribute values for currentobject instances of it, and in some cases changing the attribute values forinstances of it.

managed object classThe formal description of a set of managed objects. A managed object is thecollection of data that represents a managed resource. Specified in ITURecommendation X.701 | ISO/IEC 10040.

managed resourceA device or component in a network whose status or behavior is representedby a managed object.

managed systemA network node running a network-management agent and providing networkdata to a managing system on request.

managing systemThe system requesting information from and setting information in a networknode running a network-management system.

view iconAn icon in Solstice EM that represents one view in a set of nested views. Theicon is displayed on the next higher-level view. You can use the view iconprovided with Solstice EM or define view icons of your own.

MetaDataThe set of descriptions of the forms of data used to describe managed objects ina network (as distinct from the data itself).

MDRMetaData Repository. Within the Solstice EM Management Information Tree,the storage devoted to the descriptions of data formats.

MIBManagement Information Base. A hierarchical system for classifyinginformation about resources in a network. By industry agreement, individualdevelopers are assigned portions of the tree structure to which they may attachdescriptions specific to their own devices.

Glossary-13

MIB IIAn extension to the SNMP MIB.

MIB moduleA collection of managed objects.

MISManagement Information Server. The Solstice EM software process that servesnetwork management clients. The process running on a network workstationor server that maintains network management information in a databaseaccording to the definitions in its MIT, provides polling, filtering, logging, andother services to Solstice EM services and various other applications.

MITManagement Information Tree. A naming tree for an MIS or a set of MISs. Thestructure that organizes access to all information stored in the Solstice EM MIS.Each object within the tree is identified by its Fully Distinguished Name(FDN), corresponding to the path through the tree to reach it.

MOCManaged Object Class. In Solstice EM, a class for the description of classes ofmanaged objects. An instance of MOC is a specific class.

MOIManaged Object Instance. In Solstice EM, each set of facts about specificmanaged resources is stored in an object that is an instance of an MO (or of aclass derived from an MO).

MPAManagement Protocol Adaptor. In Solstice EM, the CMIP MPA providescommunication services between OSI managed resources and the Solstice EMManagement Information Server (MIS) via the CMIP protocol.

MRMMessage Routing Module. In Solstice EM, the module that decodes thedestination of a received message and transmits it to the appropriate part ofthe MIS. The Message Routing Module serves both messages transmittedthrough the network from network agents and messages sent internally fromone portion of the MIS to another.


nameA Fully Distinguished Name (FDN) in the MIT specifies the complete path to aManaged Object Instance. A Relative Distinguished Name (RDN) specifies thepath to a managed object instance beginning from its parent. The FullyDistinguished Name consists of concatenated Object IDentifier (OID)-valuepairs, one pair for each junction down the tree.

network elementSee element.

network management agentThe implementation of a network management protocol (a program) thatexchanges network management information with a network managementstation.

network management protocolThe protocol used to convey management information.

network management stationA computer on the network running Solstice EM.

NMFNetwork Management Forum. An association of vendors and developers ofnetwork hardware and software dedicated to the promotion of interoperablenetwork management based on the use of OSI techniques.

non-container iconIn the Viewer application, an icon for an object that cannot contain any objects.Examples of non-container icons are hosts, routers, links, and hubs. A non-container icon is distinguished from a container icon.

notificationA message reporting the status of a managed object. In Solstice EM, everynotification is passed to the request facilities and to all existing log objects(which decide for themselves what, if anything, to do with it). The set ofnotifications that the request facilities knows about—and therefore thenotifications that you can receive through a request—are defined in GDMOdocuments which are compiled into the MIS.

Glossary-15

OAMObject Access Module. In Solstice EM, translates requests for information thatrefer to objects in network terminology (for example, by network addresses orby the distinguished names of objects in the Management Information Tree) tothe methods required to access the C++ objects in which data is stored withinthe MIS.

objectIn a MIB, an object class or attribute [S]. For Solstice EM applications, acollection of data that describes a manageable network element. Objects can bephysical or logical. Examples of physical objects are network nodes; examplesof logical objects are views and their icons, requests, and queues. [C].The term object is used in several senses. In the OSI and Forum terminologyfor network management, an object is any device, process, or event that can bemanaged. In object-oriented programming such as the C++ in which SolsticeEM is written, an object is similarly any process or device represented by adata structure, with methods (functions) provided by the class to which theobject belongs. Solstice EM benefits from treating objects in the OSI/Forumsense as objects in the C++ sense.

object classThe particular set of attributes that defines an object instance. The object classcan have children object classes in the form of a tree beneath it. In the CMIPenvironment, an SNMP MIB is an object class, and each base object in the MIBis an object class.An object class can be managed; the values of its attributes for each classinstance can be polled, which implies that a software agent running on a nodecan report the instance values of the attributes to Solstice EM. See also ClassInstance and Attribute.In Solstice EM, you are sometimes required to specify a class instance. Forexample, if the object class comprises port information for a router port, youcould specify an instance of the object class by providing a router board andport number for a particular port. The information you provide to specify aclass instance is called the Instance Identifier; synonyms are RelativeDistinguished Name, Index, Instance String, and Named Object. Solstice EMalso uses the term Instance Syntax. In Solstice EM, an object class is a type ofproperty. Property groups contain two types of properties: object classes,which can be managed, and user-defined strings, which are used to define andlimit the scope of polls and requests.


OIDObject IDentifier. A number that identifies an object’s position in a globalobject registration tree. An example is 1.3.6.1.4.1.45.1.3.2, which corresponds toios.org.dod.internet.private.enterprise.synoptics.1.3.2, and identifies aSynoptics3000 concentrator. There can also be a MIB name for the objectidentifier (for example, cisco for a Cisco router). [S] In CMIP, one half of theRelative Distinguished Name (RDN) pair, which identifies an object’s positionin an MIT. See Name. [C]An Object IDentifier uses a system for describing an object’s class by referenceto a standard tree structure of descriptions. Each node of the tree is assigned anumber, so that an object’s identifier is a sequence of numbers. In Internetusage, the identifiers are shown as a string of numbers delimited by dots (forexample, 0.128.45.12); in the OSI context (and in Solstice EM) the numbers aredelimited by blanks and the entire sequence is surrounded by braces (forexample, {0 128 45 12}).

OMGObject Management Group. Consortium of users of object-oriented techniques.Sponsors of CORBA.

OMNIPoint 1Set of standards, implementation specifications, and tools developed by theNetwork Management Forum.

OMNIPoint PartnersThe sixteen organizations that collaborated in the formulation of OMNIPoint 1.

OSFOpen Systems Foundation. UNIX consortium including Hewlett-Packard, IBM,and DEC, founded 1988. Sponsors of DME.

OSIOpen Systems Interconnection. General name for the set of networkmanagement conventions adopted by the International StandardsOrganization. An international effort (via ISO) to facilitate communicationsamong computers of varying manufacturers and technology.

OSI/NMFOSI Network Management Forum. An OSI group formed to develop andpromulgate definitions and standards for the SNMP, PING, and CMIPprotocols.

Glossary-17

OSTCOpen Systems Testing Consortium.

OBEDObject Editor/Browser, the Solstice EM application tool used to inspect, andsometimes change, objects in the MIT.

P+M interfaceThe set of Protocols and the Messages (in those protocols) necessary forcommunication between management entities.

parentAn instance of the class containing a (child) object. [C]

PDMA Protocol Driver Module provide access to the SNMP and RPC managementprotocols for the purpose of communicating with SNMP and RPC managedobjects.

pedigreeIn the Object Editor/Browser (OBED), the sequence of names leading from theroot of the MIT to the level now in view. See also FDN.

pingPacket INternet Groper. A program that uses the ICMP protocol for requestingacknowledgment from an IP address as a way of testing its existence oraccessibility. Informally, used as a verb meaning “to send a signal to testresponse.” The program ping tests IP-level connectivity from one IP addressto another.

PMIPortable Management Interface. Within the Solstice EM MIS, the set of widelyused classes and functions that provide fundamental services.

pollA periodic request for MIB or MIT object-class status information sent to amanaged object. Configurable in some cases by the network administrator viaSolstice EM Request Designer. SNMP tends to be poll-oriented, while CMIPtends to be event-oriented.

pollingThe process by which the request facilities in the MIS periodically obtain datafrom an agent according to the specifications of a request template. The goal ofpolling is to obtain the attributes of a managed object.


poll rateSpecifies the delay until the first poll and the interval between successive polls.The Request Designer associates a name and a number (of seconds) with eachpoll rate. This application offers a ready-made list of poll rates and allows youto create your own poll rate.Upon the conclusion of a poll rate interval, the request facilities begin to test theconditions for the transitions that lead from a given state.Each state has a poll rate and a severity associated with it.

protocolA set of rules used by computers to communicate with each other. A protocolis also the private language and procedures of an OSI layer.

proxyA virtual object standing for some other object that cannot be addresseddirectly (because it’s outside the domain of interest or because it requires adifferent protocol). The Solstice EM MIS (which uses CMIP for its internalprotocol) creates a proxy to represent each SNMP agent with which it deals.The proxy then “speaks” Solstice EM’s CMIS-like protocol internally, but usesSNMP to converse with SNMP agents.

proxy agentSoftware running on a node that responds to and reports current informationabout another node to the Solstice EM MIS, which has no agent running on it.See also Agent. It is often used to shield network devices from CMIP overhead.

requestThe series of activities through which the request facilities in the MIS poll for theattributes of and receive notifications from the agents of managed objects. Arequest is based on a request template and is targeted on a specific managedobject. Each request is made up of multiple states, with, potentially, multipletransitions between those states.You launch requests in the Requests window, which is started from the Viewer.Once started, a requests remain alive until you stop it, in the Request Monitor.

Request Condition Language (RCL)A C-like language used to create conditions for use in requests.

request facilitiesThat portion of the MIS that polls and receives notifications from the agents ofmanaged objects. The main job of the request facilities is to start and maintainrequests.

Glossary-19

request templateThe specific form of a request, as created in the Request Designer. Any numberof requests can be built on a single request template. A request templatecontains the states, conditions, and transitions that make up a request. Eachrequest template has a name, which you can use in other applications to start,stop, or view a request. When you start a request, you are applying a specificrequest template to a specific managed object.

resourceIn UNIX and X parlance, a file that contains set-up information that anapplication may consult during its operation (typically, when it is initialized)specifying values for fonts, colors, etc.

RDNRelative Distinguished Name. The AVA that identifies a managed object whenits parent’s Fully Distinguished Name (FDN) is given.

RFCRequest for Comment. The series of documents that formalize protocols withinthe Internet (TCP/IP-based) community are referred to as RFC, the last phasein the formal standardization process before the document is made official.RFCs are published by the Internet Engineering Task Force (IETF).

ROSERemote Operation Service Entry.

routerThe term routing refers to the process of selecting a path over which to sendpackets, and router is any computer able to make such a selection. Althoughboth hosts and gateways do routing, the term router is commonly used for adevice that interconnects two networks (See gateway).

RPC PDM

Remote Procedure Call Protocol Driver Module. The RPC PDM provides themechanism to get data and set attribute values for devices that are managedvia RPC based agents. The RPC PDM works as a proxy agent between theSolstice EM MIS (Management Information Server) and any device on thenetwork having RPC agents installed on it.The RPC PDM serves a major role in providing compatibility with SunNetManager 2.2 or later products.


SAPService Access Point.The notional point at which a service user and a layerentity can meet so that services can be offered by the layer entity to theparticular user.

Schema compilerSNM 2.x schema files get compiled by the schema compiler (em_snm2gdmo)into GDMO and ASN.1 descriptions which then get loaded into the SolsticeEM MIS by other utilities. Users can then send requests to the MIS which getforwarded to the RPC PDM.

scopeIn general, a definition of the extent or boundaries of an action to be taken. Forexample, a poll’s scope is the set of nodes and/or lines to be polled. InDiscover, scope refers to the top level of a subnet, represented as a cloud icon.Scoping identifies the sub-tree of the MIT on which a filter is to be applied.CMIP scoping and filtering help reduce traffic overhead from managementprotocols.The sub-tree within a Management Information Tree to which a managementcommand is to be applied. The scope is described by the node of the parenttree at which the sub-tree is rooted, and the depth (number of nodes) to whichthe scope extends.Typically, a network command is qualified both by its scope and by a filter thatfurther selects objects with the scope.

severityDescribes the degree of importance you attach to each state in a request. Aseverity is made up of three items: a name, a number, and a color. The severitycolor is reflected in the color of the icon for the managed object as that object isdisplayed in the Viewer. The Request Designer offers a ready-made list ofseverities and allows you to create your own severity.Each state has a severity and a poll rate associated with it.

shared conceptual schemaBasis for cooperation between managers:

• Management functions• Managed object classes• Available instances of the managed object classes• Authorization

Glossary-21

sieveIn terminology of the Network Management Forum, an object that decideswhether and where to forward a notification received from a managed object.Superseded by the OMNIPoint 1 term “event forwarding discriminator” (EFD).

SMAESystem Management Application Entity. OSI terminology for a software MISthat manages a network: for example, Solstice EM.

SMIStructure of Managed Information. General term for various ways ofspecifying the information available about an object (including GDMO objectdescriptions, MIBs, and so on).

SNMSunNet Manager.

SNMPSimple Network Management Protocol. Protocol for exchanging informationbetween network managers and “agents” processes within various managedobjects that are able to report their status on request. The protocol wasintroduced as a simple interim solution, but is at present widely used in theInternet environment. It is a connection-less protocol, with the view ofcontinuing to receive information from managed objects even when networkperformance is degraded and a connection-based reliable transport may fail.

SNMP PDMSNMP Protocol Driver Module. Allows for the getting of data and the settingof attribute values for SNMP managed devices. The SNMP PDM works as aproxy agent between the Solstice EM MIS (Management Information Server)and any device on the network which is SNMP-manageable.

siblingAn object that shares a common parent class with the object in question. [C]

stateA description of a managed object in a point in time with respect to a request.At any given moment, a request, reflecting the target managed object, is insome state defined in that request or is undergoing a transition between states.


You can think of a state as a receptacle that holds transitions to other states.While in a state, a request repeatedly, at intervals determined by the state’s pollrate, tests the conditions associated with each transition leading from that state.In addition to a poll rate, each state has a severity associated with it. It also hasa name and a description. Between any two states, there is a single transition(one-way or two-way) with, potentially, multiple conditions associated witheach transition.There is one required state, the ground (or init) state. The only requirement forthis state is that it have a severity of “normal”. Other states are of yourchoosing.

subnetIn Internet parlance, a logical partition of a network. OSI attaches a morerestricted meaning: the portion of a network attached to the same physicalmedium.

subnet maskA 32-bit quantity indicating which bits in an IP address identify the physicalnetwork.

system objectAlso known as agentCME object. An Solstice EM MIS running on a networknode.

TCP/IPTransmission Control Protocol/Internet Protocol. The Internet suite ofprotocols is a group of protocols related to a common framework, or set ofrules that defines how computers communicate with each other in an open(non-proprietary) system, typically a large communications infrastructure.

TMNTelecommunications Management Network. A model proposed by the ITU.

tableAn SNMP term that describes a set of attribute values for object class instances.The rows represent the attributes and the columns represent class instances.

top classIn the Network Management Forum system for the description of managedobjects in a network, the root class from which all other classes are derived.

Glossary-23

tracerouteA program that attempts to reconstruct the route from (and hence to) an IPaddress.

transactionIn database terminology, a sequence of operations that are to be regarded as an“atom” —that is, as indivisible. Either the entire set takes place, or none of it.In practice, this means that the database must be able to back of a transactionthat is aborted, so that data are left as they were before the transaction wasattempted.

transitionIn the context of requests, the change from one state to another, which occurswhen a condition associated with a transition evaluates to true. From one state,a request can make transitions to multiple states, including the state from whichthe transition started. Within a pair of states (or from and to itself) there can bea single transition. Each transition is associated with one or more conditions.Where there are multiple conditions, the request facilities evaluate conditions inthe order they are entered in the request template.When a transition occurs, depending on the specifications in the requesttemplate, a set of actions might be performed, to, for example, set variables orsend notifications.

trapIn Internet jargon, notification of a problem that an agent sends to amanagement MIS of its own initiative rather than in response to a poll. SNMPformally defines seven types of traps and permits subtypes to be defined.OMNIPoint 1 uses the term “event report” rather than “trap”.

trap-directed pollingA hybrid form of trouble reporting in which a single trap initiated by an agentis followed up by polls in which the management MIS requests furtherinformation.

triggerThe condition that causes a state transition.

UDPUniversal Datagram Protocol. A connectionless protocol over which SNMP isusually implemented.


variableA quantity associated with a managed object that, along with attributes, is thetarget of a polling operation. The Request Condition Language (RCL) allows youto specify variables as you need them when you create a condition. It typesthese variables at runtime. The RCL also has a set of system variables, whichyou will find useful in a variety of different request templates.

ViewerThe Solstice EM application that manages and displays a graphicrepresentation of a set of managed objects in a network.

viewIn Solstice EM, a graphic representation of a set of managed objects in anetwork, as presented by the Viewer application. A view can be part of ahierarchy, imitating the tree-form of a network topology, or non-hierarchical,wherein it is a logical grouping of managed objects in a flat space. In SolsticeEM, a view is equivalent to a container icon.

view objectA collection of lines and icons that you situate in a set of views with optional,appropriate background pictures for the views to represent your network andits subnets.

view fileA text file that holds your network’s configuration information: the filenamesof view and subview background pictures; the filenames and positions of iconsrepresenting computers, routers, hubs, and lines; poll, mask, and requestconfiguration information; and property groups. Also called a View DatabaseFile or View_db File.

XOMX/Open OSI/ASN.1 Manipulation. Specification of a wrapper around ASN.1intended to offer the programmer a simplified API for ASN.1.

XMPX/Open Management Protocol. An API (also known as CM-API). It provides amanagement service interface to support the use of both CMIP and SNMPprotocols by management applications.

Index-1

Index

Symbols—, 11-11.em_viewer.cf configuration file, 10-21,

10-67

AAbstract Syntax Notation One

(ASN.1), 3-3Access Manager

Access Privileges, 9-35Applications Folders, 9-35Create Group window, 9-19Create User window, 9-27directories under filter, 9-16, 18-7Duplicate Group window, 9-25Duplicate User window, 9-31Export Customized window, 9-10Feature Access privileges, 9-36filter selection, 9-14, 9-16, 18-7Find window, 9-33Forms Display, 9-20full access, 9-36Group Members, 9-22Group Privileges, 9-22Group Properties, 9-24groups, 9-2Groups/Application Privileges, 9-10Import from File, 9-13

managed groups, 9-28Match On selection, 9-33no access, 9-35Object menu, 9-18printer selection, 9-17purpose, 9-1starting, 9-6user levels, 9-2user login ID, 9-27User Privileges window, 9-35User Properties window, 9-30View menu, 9-32

Access Manager main window, 9-8Access Manager security, 16-2Access Privileges, Access Manager, 9-35access to managed resources via

CMIP, 4-3acknowledging an alarm, 15-17Activations, default, 10-71Address Resolution Protocol (ARP)

in Discover, 11-6, 11-12agent

MIS as, 7-2proxy, 1-7

agent, browser, 16-8agents, 4-3alarm

definition, 15-1

Index-2 Solstice Enterprise Manager Reference Manual

alarm associations, 15-31alarm counters, 6-2alarm instances

accessing information on, 15-6Alarm Instances window, 15-6Alarm Manager, 15-1

alarm associations, 15-4, 15-22alarm filtering criteria, 15-11, 15-31Alarm Instances window, 15-7alarm states, 15-10alarm summary properties, 15-24Alarms Criteria window, 15-31Alarms Filter window, 15-11association grouping criteria, 15-32changing alarm states, 15-16, 15-30configuration file formats, 15-34displaying a summary of all

alarms, 15-11, 15-31displaying logs, 15-12Edit menu options, 15-17File menu option, 15-11filter configuration file format, 15-34Filter Properties, 15-19Graph Criteria window, 15-29, 18-2Graph window, 15-29grouping by alarm severity, 15-3grouping by device, 15-3how it displays alarm

notifications, 6-10invoking from Viewer, 10-58invoking the Grapher

application, 15-30main window, definition of, 15-10manipulating log records, 5-2Object menu options, 15-16starting, 10-58, 15-1

from the command line, 15-2Summary window, 15-3View menu options, 15-18View Properties sheet, 15-23

Alarm Servicelogging non-default alarms to the

AlarmLog, 6-9Overview, 6-1turning off, 6-10

what it is, 2-5, 6-1which alarm logs to monitor, 6-9

Alarm Service in Actiona scenario, 6-6

alarm service scenario, 6-6Alarm Severity, Viewer, 10-29alarm states, 15-30AlarmLog, 6-2, 13-2

alarm types logged in, 6-2discriminator construct, 6-3

alarms criteriasamples, 15-11, 15-31

Alarms Managerinvoking from Viewer, 10-61

APIsLL (Low-Level), 1-10

applicationclient, 1-7

Application Launcher, 8-1Configure Applications window, 8-5invoking the Alarm Manager, 15-1starting Discover, 11-2starting the Data Collector, 12-3starting the Log Viewer, 14-1starting the SNMP Browser, 16-3starting the Viewer, 9-6, 10-5

Applications Folders, AccessManager, 9-35

applications, Tools, Viewer, 10-43arguments for executable, 10-43ASN.1, 4-9

definition, 1-6, 3-4ASN.1 compiler, 2-4

em_asn1, 23-10, 23-22ASN.1 compiler (em_asn1), 3-1, 3-3, 3-4,

3-12ASN.1 definitions, new

directory for, 1-6ASN.1 descriptions, 3-10ASN.1 document, 3-15ASN.1 documents, 3-10

provided with this product, 3-4ASN.1 format, 3-4

Index-3

ASN.1 type-definitions, 3-4Association Properties window, 15-21Attribute List window, Data

Collector, 12-10Attribute Value Assertion(AVA)

defined, 7-3Attributes

Read Only Fields, 20-17Attributes Table

Browser, 16-9attributeValueChange

mapped to log record type, 5-5auto management daemon

receiving event notifications, 22-8autoEntryKey field, 22-4autoEntryScope field, 22-4autoEntryTemplate field, 22-3autoEntryTopoType field, 22-4autoManagementEntry objects

changing the administrativeStateattribute, 22-7

default administrativeStatevalue, 22-6

automatic managementcomponents of, 22-1how to start/stop, 22-6

automatic management objectactivating and deactivating, 22-2how to create, 22-2

automatic management objectscreation during installation, 22-2

BBackground Properties, Viewer, 10-31backup

of runtime database, 2-14bitmap (sunraster), Viewer, 10-32browse log records

how to, 13-1Browser default agent, 16-21

Cclass, 1-5

managed object, 1-5clearing an alarm, 15-17client applications, 1-7CMIP, 20-2CMIP Configuration window

how to invoke, 19-4how to retrieve, 19-11

CMIP descriptions, 3-13CMIP message

ACTION request, 4-5ACTION response, 4-6CANCEL-GET request, 4-7CANCEL-GET response, 4-8CREATE request, 4-6CREATE response, 4-7DELETE request, 4-7DELETE response, 4-7EVENT request, 4-8EVENT response, 4-8GET request, 4-4GET response, 4-4SET request, 4-5SET response, 4-5

CMIP messages, 4-3event notifications, 4-3request, 4-3

CMIP MPA, 2-4, 4-1, 4-2providing distributed processing, 4-2services provided, 4-2starting, 4-3trap handling, 4-3unsolicited notifications, 4-3

CMIP NotificationsLogging to AlarmLog, 6-3

CMIP Proxy Agent, 4-3CMIP stack, 4-3, 4-4CMIS like primitives, 4-2CMIS-like, 4-10CMIS-like message, 4-10CMIS-like request, 4-9coded logID, 5-15


Color Editor, Viewer, 10-28color mapping

changing the default, 6-11default, 6-11

columns for displaying icons,Viewer, 10-38

Command Linestarting Discover, 11-2

Command Line Options, 23-1Common Management Information

Protocol (CMIP), 4-1communicationsAlarm

mapped to log record type, 5-5community strings

specifying in Object Configurationtool, CMIPconfiguration, 19-17

specifying in Object Configurationtool, SNMPconfiguration, 19-20

Concise MIB compilercommand line options, 3-13convert to ASN.1 format, 3-11convert to GDMO format, 3-11description, 3-10files generated, 3-10OIDs, 3-13OIDs imported, 3-11processing its output files, 3-12syntax errors, 3-15

Concise MIB compiler (em_cmib2gdmo), 3-1, 3-3, 3-10, 3-12,4-9

Configure Device Options window,Viewer, 10-46

Configure Tools window, Viewer, 10-41Configuring the MIS to run as non-

root, 2-14configuring Viewer icons, 10-60connection icon

creating in Viewer, 10-17container icon, 10-2containment, 1-4

converting SNM 2.x schema files toGDMO descriptions, 3-15

CREATE entriesexamples, 22-4

CREATE entry, 22-3examples, 22-3

Create Group window, AccessManager, 9-19

Create User window, AccessManager, 9-27

creating Viewer icons, 10-60

DData Collection Entry object, 12-2Data Collector

Attribute List window, 12-10Create Collection window, 12-6Edit Collection window, 12-13File Wrapping, 12-11GDMO classes, 12-14Max File Size, 12-11max file size, 12-2Object Attributes list, 12-9Object Attributes selection, 12-9Object Browser, 12-7object list, 12-6Poll Interval, 12-11Request menu, 12-5request objects, 12-1Start Time, 12-12Start/Stop Date, 12-12starting, 12-3starting from command line, 12-3starting from Launcher, 12-3Write Attribute Name, 12-12Write Document Name, 12-11

Data Collector daemon, 12-2Data Collector main window, 12-4Data Collector menu, 12-5Data Collector, overview, 12-1Data Viewer

Inspect Criteria, 17-5invoking, 17-3

Index-5

overview, 17-1polling frequency, 17-6polling interval, 17-6sending a get a request, 17-5start polling, 17-6starting from command line, 17-2starting from Viewer

application, 17-3target object, 17-4Target Object field, 17-5

Data Viewer and the PMI, 17-1Data Viewer main window, 17-4Database Schema Mapping, 5-15Database Schema Parser, 5-25dataCollectorEntry object, 12-15DBM database, 2-5debug agent

how to turn off, 23-15sending message to stdout, 23-15starting and stopping multiple

agents, 23-15debug agents, 23-13

dynamically enabled using em_debug, 23-13

list of common agents, 23-14Nerve Center debugging

agents, 23-15statically enabled, 23-13turning all of them on, 23-15

debug server, 23-13Debugging

em_debug utility, 23-13debugging

options for Discover, 11-24Default Activations window,

Viewer, 10-49default agents

creating, 19-11default installation directory, 3-1default MO Name, 19-11default MO RDN, 19-11default preferences in Viewer, 10-21Delete selections, browser, 16-16

directories under filter, AccessManager, 9-16, 18-7

Discovercommand line options, 11-20configuration options, 11-2debugging options, 11-24method of search, 11-5Network Security, 11-7ports used to probe network, 11-7Properties sheet, 11-7Start Discover, 11-4starting, 11-2

Discover Propertiesagent mapping field, 11-14default proxy, 11-11default view, how to specify, 11-13gateways field, 11-14general field, 11-12hop count, 11-10ICMP retries, 11-10ICMP timeout, 11-10ICMP/SNMP Field, 11-9netmask, how to specify, 11-14network, how to specify, 11-13objects field, 11-11objects, hosts, 11-11objects, links, 11-11objects, routers, 11-11objects, SNMP devices, 11-11search method, ARP, 11-12search method, Default, 11-12search method, how to specify, 11-12search method, serial ping, 11-12SNMP read community, 11-9SNMP read community, maximum

number of names, 11-9SNMP retries, 11-10SNMP Timeout, 11-9SNMP write community, 11-9view creation, flat view, 11-13view creation, hierarchy view, 11-13view creation, how to specify, 11-13

discriminator constructwhat it is, 13-2

Display


Object Layers, 10-37Display map layers, Viewer, 10-37displaying

detail log records, 14-4displaying alarm files, 15-12displaying log records, 14-6distinguished name(DN)

defined, 7-3distributed multi-user access, 2-2Drag and Drop icon, browser, 16-12Duplicate Group window, Access

Manager, 9-25Duplicate User window, Access

Manager, 9-31

EEdit Collection window, Data

Collector, 12-13Edit menu

Paste, 10-17EFD

definition, 7-8element icon, 10-2elements

pasting, 10-17EM, 1-1em command

optional parameters, 8-2, 23-2starting the Application

Launcher, 23-2em_accesscmd, 9-2

starting the Access Controlapplication, 23-2

supported commands, 23-3third party applications, 23-2

em_accesscmd commandoptional parameters, 23-3

em_accessmgrstarting Access Manager, 23-5

em_accessmgr commandoptional parameters, 9-7, 23-6

em_alarmmgr

starting the Alarm Manager, 23-6em_alarmmgr command, 14-2, 15-2

optional parameters, 23-6em_alarmmgr_fp.cf file format, 15-34em_asn1

starting the ANS.1 compiler, 23-7em_asn1 command

optional parameters, 3-5, 23-7em_asn1 compiler, 3-3, 3-11em_asn1comp compiler, 3-1em_autod daemon, 2-7, 2-8

monitor object creation anddeletion, 23-7

optional parameters, 23-8em_automgrd

how to start/stop, 22-7em_automgrd daemon, 22-7em_cmib2gdmo

invoking the Concise MIBcompiler, 23-8

em_cmib2gdmo commandoptional parameters, 23-8

em_cmib2gdmo compiler, 3-1, 3-3, 3-10,4-9

em_cmip daemon, 2-7, 2-13implementing CMIP MPA

functions, 23-9em_cmipconfig

replaced by -cmip option of em_oct, 23-34

replacing, 19-11em_compose_all command

before running, 23-9command line arguments, 23-10what it does, 23-9

em_compose_oc commandcommand line arguments, 23-10prior to running, 23-10what it does, 23-10

em_compose_poc commandcommand line arguments, 23-11prior to running, 23-10what it does, 23-10

Index-7

em_datacollectorstarting the Data Collector, 23-11

em_datacollector commandoptional parameters, 12-3, 23-11

em_datad, 12-2what it is, 23-11

em_datad daemon, 2-7, 2-8optional parameters, 23-12

em_dataviewerstarting the Data Viewer, 23-12

em_dataviewer commandoptional parameters, 23-12

em_debugoutput for dynamically enabled

agents, 23-13output for statically enabled

agents, 23-13starting the MIS debugging

features, 23-13em_debug command, 23-15

optional parameters, 23-14overview, 23-13

em_discoverdebugging, 23-19starting Discover, 23-16starting Monitor, 23-17

em_discover commandoptional parameters, 23-16

em_dmuxd daemon, 4-9em_gdmo

invoking the GDMO compiler, 23-20parse-and-compile operation, 23-21parse-only operation, 23-21two modes of operation, 23-20

em_gdmo commandoptional parameters, 3-8, 23-20

em_gdmo compiler, 3-1, 3-3, 3-11specifying a header string, 3-8

EM_GOTOVIEW command, 10-49em_grapher

starting the Grapher, 23-21em_help

starting online help, 23-21

EM_HLOG_DIR environmentvariable, 5-6

EM_HLOG_INTERVAL environmentvariable, 5-6

EM_HOME environment variable, 13-23em_imex

importing and exporting logobjects, 23-22

em_imex commandoptional parameters, 23-22

em_key_rninternal foreign key, 5-15

em_load_name_bindingsbefore running this command, 23-22command line arguments, 23-23what it does, 23-22

em_load_nc_templateswhat it is, 23-23

em_log2rdb commandoptional parameters, 5-26, 23-24

em_log2rdb daemon, 5-8how to start, 5-25what is it, 5-25

em_login daemon, 2-5, 2-8password authentication, 23-24

em_logmgrstarting the Log Manager, 23-24

em_logmgr commandoptional parameters, 23-25

em_logviewstarting the Log Viewer, 23-25

em_logview commandoptional parameters, 23-26

em_mis daemon, 2-6, 2-8em_mismgr

starting the MIS Manager, 23-26em_mismgr command

optional parameters, 23-26em_ncam

handling Nerve Center action, 23-27em_ncam daemon, 2-6, 2-8em_ncexport


starting the Nerve Center Exportutility, 23-27

em_ncexport commandoptional parameters, 23-28

em_ncexport utility, 2-10em_ncimport

starting the Nerve Center Importutility, 23-28

em_ncimport commandoptional parameters, 23-29

em_nnaddstarting the Nickname Service

Addition utility, 23-29em_nnadd command

optional parameters, 23-30em_nnconfig

input file format, 23-30sample input file, 23-31starting the Nickname Service

Configuration utility, 23-30em_nnmpa

starting the Nickname Service MPA,starting the global nicknameserver, 23-31

em_nnmpa daemon, 2-8what it is, 2-7

em_obcodegenstarting the Object Code Generator

(OCG), 23-32em_obcodegen command

optional parameters, 23-32em_obed

starting OBED, 23-33em_obed command

optional parameters, 23-33em_objop

start a UNIX utility that allows you tosend CREATE, SET, DERIVE,and DELETE requests to anMIS, 23-33

em_objop commandcreating autoManagementEntry

objects, 22-3

em_octstarting OCT, 23-34

em_oct commandoptional parameters, 23-34

em_reqeditstarting the Request Designer, 23-35

em_reqedit commandoptional parameters, 23-35

em_schema2gdmo compiler, 4-9em_services

restarting the MIS, 23-35em_services command, 2-8, 2-10

optional parameters, 23-36em_snm2gdmo

invoke the Schema compiler, 23-37em_snm2gdmo compiler, 3-1, 3-4, 3-15em_snmdb_import command

optional parameters, 23-37em_snmfwd

forward SNM traps to the MIS, 23-38em_snmfwd daemon, 2-6, 2-8

optional parameters, 23-38em_snmpbrowser

starting the SNMP Browser, 23-39em_snmpbrowser command

optional parameters, 23-39em_snmp-trap daemon, 2-6em_snm-trap daemon, 2-8em_this_rn

internal primary key, 5-15em_topoimex

starting the Topology Import/ExportTool, 23-39

em_viewerstarting the Viewer, 23-41

em_viewer commandoptional parameters, 23-41

EM_VIEWERCONFIG command, 10-49EM-config configuration file, 4-3emLogHist table, 5-17Enterprise Manager, 1-1environment variable

Index-9

EM_CMIP_MPA_DEFAULT_HOST, 4-4

EM_HOME, 14-21, 15-34EM_MIS_DEFAULT_HOST, 4-3, 4-4EM_SERVER, xliiitable, B-1

environmentalAlarmmapped to log record type, 5-5

equipmentAlarmmapped to log record type, 5-5

Event Forwarding Discriminator (EFD)definition, 7-8

event handling, 2-2event record types

dynamic addition, 5-25eventLog table, 5-15executable arguments, 10-43

FFDN, 1-5, 5-3FDN translation, 2-7Feature Access privileges, Access

Manager, 9-36File Selection window, browser

SNMP BrowserFile Selection window, 16-14

File Wrapping, Data Collector, 12-11Filter

Viewer, 10-33filter, Access Manager, 9-14, 9-16, 18-7Find Results area, Viewer, 10-52Find window, Access Manager, 9-33Find window, Viewer, 10-51Fixed Icon Size button, 10-24Forms Display, Access Manager, 9-20full access, Access Manager, 9-36fully distinguished name, 1-5Fully Distinguished Name (FDN), 5-3

GGDMO, 4-9

description, 1-5GDMO classes, Data Collector, 12-14GDMO compiler, 2-4

em_gdmo, 23-9, 23-10, 23-22input, 3-6input files, 3-12invoking, 3-8parse-and-compile mode, 3-9parse-only mode, 3-9what it does, 3-6

GDMO compiler (em_gdmo), 3-1, 3-3,3-10, 3-13, 3-15

GDMO definitions and documents, 3-7GDMO description

format, 3-6GDMO descriptions, 3-10GDMO document, 3-10, 3-15GDMO document format, 3-6GDMO documents

compiler, 3-7parsing, 3-7

GDMO documents provided with thisproduct, 3-6

GDMO format, 3-4geographical map file, 10-66Geographical map files, Viewer, 10-65Geographical Map, Viewer, 10-32geographical view style, 10-23Get/Set request, Viewer, 10-60global nickname server, 2-7

adding to the MIS, 23-29populating, 23-30

Grab Color button, 10-28Grapher

Edit options, 18-16overview, 18-1Property Modifier window, 18-1scaling, 18-17zooming, 18-16

graphical editorpasting elements, 10-17

Group Members, Access Manager, 9-22Group Privileges, Access Manager, 9-22


Group Properties, Access Manager, 9-24groups, Access Manager, 9-2Groups/Application Privileges, Access

Manager, 9-10GUI applications

invoking, 23-1

HHistorical Log File format, 5-7historical log files

naming convention, 5-7what they store, 5-8

Historical logging, 5-1historical logging

configuration file, what itcontains, 5-9

database schema definition file, 5-10enabling, 5-6purpose, 5-6

Historical Relational Database (RDB)Logging, 5-8

-host parameterspecifying a hostname, 23-2

Iicon

configuring for Viewer, 10-60container, 10-2creating for Viewer, 10-60element, 10-2multimonitor, 10-2

Icon Label sizeViewer, 10-25

Icon Menu parameters, 10-70Icon Size parameters, 10-23Icon Status Color Source

Viewer, 10-29icons, 10-17, 10-57IIMCIMIBTRANS, E-8IIMCMIB-II, E-8IIMCOMIBTRANS, E-8IIMCPROXY, E-9

IIMCSEC, E-9Import from File, Access Manager, 9-13increment of jump

Viewer, 10-25instance

definition of, 1-5integrityViolation

mapped to log record type, 5-5internetAlarm

mapped to log record type, 5-6internetAlarms

logging to AlarmLog, 6-3ISO, E-1ISO naming, 2-2

Llaunching applications, 8-1Layers section, Viewer, 10-71layout function in Viewer, 10-19Layout window, Viewer, 10-38levels of control, Access Manager, 9-2link icon

creating in Viewer, 10-17LL API, 1-10local object, 1-6log

notification type, 13-2log discriminator, 13-3log management

activities involved, 5-1Log Manager

Configure Tools option, 13-14creating a new log object, 13-9creating log objects, 5-2Deleting selected log objects, 13-11Deselect All option, 13-12discriminator construct, 13-4Export File option, 13-8Import File option, 13-8invoking from Viewer, 10-58Log Object window, 13-9

Index-11

modifying properties of a selected logobject, 13-11

New option, 13-9optional command line

parameters, 13-5Print option, 13-8Properties option, 13-7Select All option, 13-12starting, 10-58, 13-4what it is, 13-1

Log objectAttributes, 13-2

Administrative state, 13-3Capacity, 13-2Discriminator, 13-2Name, 13-2

log objectadding log records, 5-4attributes, 5-3

administrativeState, 5-3currentLogSize, 5-3discriminatorConstruct, 5-3logFullAction, 5-3maxLogSize, 5-3Name, 5-3nameBinding, 5-3numberOfRecords, 5-3objectClass, 5-3operationalState, 5-3

deleting, 5-4what is it, 13-1

Log Objectsadding to the AlarmLog, 6-9

log objectscreation of, 6-2deleting, 6-10number in MIS, 13-2removing from emAlarmLogList

using Log Manager, 6-10removing from emAlarmLogList

using OBED, 6-10log record creation

notifying the Alarm Service, 6-2log record events

common attributes, 5-7

Log recordshow they are derived, 5-25

log records, 13-1adding to a log object, 5-4creating, 5-4defining new types, 5-25deleting, 5-4detailed data, 14-4displaying, 14-6log full action, 5-4viewing detailed, 14-12

log sizelimitation, 5-6

Log Viewerconfiguration files, 13-5, 14-2deleting a log record, 14-7detailed records, 14-12displaying logs, 14-6exiting, 14-7exiting, saving changes, 14-7Find a log record, 14-7invoking from Viewer, 10-59Log Properties option, 14-6Print option, 14-6starting, 10-59, 14-1

from ApplicationLauncher, 14-1from the command line, 14-2

loggingdiscriminator construct, 13-11

object identifiers, 13-18notification types, 13-17

logging notification records, 13-3logging services, 5-1logical layers, Viewer, 10-35logical view

definition of, 10-59logical views, 10-5logical views in Viewer, 10-5Low-Level API, 1-10

Mmanaged groups, Access Manager, 9-28managed object, 1-4, 1-5


in Object Configuration tool, 19-1naming requirements, 7-2

managed object class, 1-5managed object instance, 1-6managed objects, 2-2, 2-4

defined, 7-1managed resource

definition of, 1-5managed resources, 4-3Management Information Bases

(MIBs), 4-9Management Information Server

(MIS), 2-1, 3-2Management Information Tree, 5-1

mounting a section of the, 7-3Management Information Tree (MIT), 2-2,

2-3, 2-4, 3-2, 3-10, 5-3, 19-11, 20-5defined, 7-2

Management Protocol AdapterLibrary, 2-3

managerMIS as, 7-2

managing objects in multiple MISs, 7-4Map Layers, Viewer, 10-36, 10-66Map, Viewer, 10-39maps

geographical, Viewer, 10-65Match On selection, Access Manager, 9-33Max File Size, Data Collector, 12-11Maximum Percent

Viewer size, 10-24MDR, 1-3, 2-4, 3-2, 3-3, 3-7

descriptions of managed objects, 2-4how to load new GDMO managed

object descriptions, 3-6MDR directory

system data, 3-6user data, 3-6

MetaData Repository, 3-7MetaData Repository (MDR), 1-3, 2-4, 3-2MIB browser, overview, 16-1MIB information, 16-21

MIB information for browser, 16-8MIBs, 4-9Minimum Percent

Viewer size, 10-24MIS, 2-1, 2-3, 3-2

components, 2-3definition, 2-1restart without saving any data, 2-9running as non-root, 2-14start/restart and preserve the

configuration data, 2-9start/restart and reinitialize, 2-11starting immediately after a new

installation, 2-8MIS functions, 2-2MIS knowledge

instance of a class, 3-2object class, 3-2

MIS logging, 5-1MIS Manager, Viewer, 10-59MIS to MPA communication, 4-10MIT, 2-2, 3-2, 3-10, 5-3, 20-2

objects, 2-4, 3-2see Management Information

Tree, 7-2MIT (Management Information Tree), 5-1MMC

example using, 7-6MOC, 1-5Modify button, Viewer, 10-23MOI, 1-6Monitor

configuration options, 11-2invoking, 11-5

Monitor PropertiesGeneral Field, 11-17General Field, holding

container, 11-18General Field, no response

event, 11-18General Field, object down

timeout, 11-17

Index-13

General Field, time betweencycles, 11-18

Log Information field, 11-18Log Information field, log file, 11-19Log Information field, mailing a log

file, 11-19Object to Monitor field, 11-17Objects to Monitor Field,

containers, 11-17Objects to Monitor Field, ignore

objects, 11-17perceivedSeverity, 11-18Timers field, 11-19Timers field, run weekly, 11-20Timers field, start date, 11-19Timers field, start time, 11-19Timers field, stop date, 11-20Timers field, stop time, 11-19

mountinga section of the MIT, 7-3

multimonitor icondefinition of, 10-2

multiple views, searching for anobject, 10-62

NNavigator buttons, browser, 16-12Navigator orientation, 10-23Nerve Center, 2-4

condition detection, 2-4Nerve Center actions

how they get handled, 2-6Nerve Center Interface Library, 2-4Nerve Center templates

how to load, 23-23nerveCenterAlarm

mapped to log record type, 5-6nerveCenterAlarms

Logging to AlarmLog, 6-3New Agent selection, browser, 16-18Nicknames

FDN translation, 23-31no access, Access Manager, 9-35

OOBED

Containment, 20-5for Set operations, 20-18Get operations in, 20-9Object Configuration window, 20-16Path field, 20-5virtual objects, 20-1

OBED PanelAttributes, 20-13

ObjectTransitory, 20-1

objectlocal, 1-6shadow, 1-6

Object Attributes list, Data Collector, 12-9Object Attributes selection, Data

Collector, 12-9Object Browser, Data Collector, 12-7object classes

composing, 23-22Object Configuration tool

overview, 19-1starting, 19-2

Object Configuration windowin OBED, 20-15

object layers, 10-35object management services, 2-2Object menu, Access Manager, 9-18Object Palette

adding new object types to, 10-63as invoked from Viewer, 10-57

objectCreationmapped to log record type, 5-5

objectDeletionmapped to log record type, 5-5

objectsdeleting from Viewer, 10-18managing in multiple MISs, 7-4searching for, 10-62

OCTadding an agent, 19-11Agent page, 19-10


changing an agent’sconfiguration, 19-10

command line options, 19-3coordinates page, 19-21Coordinates page, geographical

coordinates, 19-22Coordinates page, logical

coordinates, 19-22default agents, 19-11Display Status page, 19-21Display Status page, configuring a

monitor object, 19-21Display Status page, severity

propagation, 19-21how configuration values for an

existing object are read, 19-8how it gets its information, 19-2how to use, 19-2invoking from the Viewer, 19-2main window, 19-4name field, 19-6Name field, changing an object

name, 19-6Name field, creating multiple

objects, 19-6Name field,adding an object

name, 19-6Object Description page, 19-7Object Description page, deleting

description fields, 19-9Object Description page, multiple

description fields, 19-9object types, list of, 19-7type field, 19-7updating information in the

MIS, 19-2when to use, 19-1

OMNIPoint, 2-4OMNIPoint 1, 3-2OmniPoint 1 log format, 5-2open state

defined, 15-10, 15-30operationalViolation

mapped to log record type, 5-5

PPaste

editing, 10-17pasting elements, 10-17PDM, 4-2, 4-9persistent data storage

definition, 23-10persistent storage, 2-2, 2-5

restarting the MIS with em_services -i, 23-10

physicalViolationmapped to log record type, 5-5

platform, 1-3PMI, 2-1, 2-2, 2-3, 4-2, 5-3

services provided, 1-9PMI components, 2-3Poll Interval, Data Collector, 12-11Poll Setup window, browser, 16-19polling

using proxy agents, 22-5polling for information, browser

SNMP Browser, polling forinformation, 16-25

Portable Management Interface (MPI), 2-3Portable Management Interface

(PMI), 2-1, 2-3, 4-2, 5-3print window, browser

SNMP Browserprint window, 16-13

Printer field, browser, 16-15printer selection, Access Manager, 9-17processingErrorAlarm

mapped to log record type, 5-5Propagated Alarm Severity, Viewer, 10-29propagating Alarm Severity, 10-61Properties, Default, Viewer, 10-40Protocol Driver Module (PDM), 4-9proxy agent, 1-7, 4-9proxy mechanism, 2-2Purge alarm from log, 15-17

Index-15

QqualityofServiceAlarm

mapped to log record type, 5-5

RRDB logging

what it is, 5-8RDB logging information

where is it retrieved from, 5-9reference OI, 4-6Relational DB logging, 5-1relationshipChange

mapped to log record type, 5-5relative distinguished name (RDN)

defined, 7-3Remote Procedure Call (RPC), 4-9Removing an alarm, 15-17repository of management definitions, 2-2request objects, 12-1request template

drag and drop, 10-55request templates, 2-4requestInfo attribute, 12-16Requests window, Viewer, 10-54Reset Properties, Viewer, 10-39RFC, E-1RFC-1214, E-9RPC, 4-2, 4-10RPC based agents, 4-9RPC calls, 4-9RPC PDM, 2-5, 4-2, 4-9, 4-10RPC PDM and manageable SNM agent

communication, 4-10RPC request, 4-10runtime database

creating backup of, 2-14

SScale Icon Size, 10-23Schema compiler

command line options, 3-15output, 3-15

Schema compiler (em_schema2gdmo), 4-9

Schema compiler (em_snm2gdmo), 3-1,3-3, 3-4, 3-15

searchingfor objects, 10-62

searching for a log record, 14-7security, browser, 16-2securityServiceorMechanismViolation

mapped to log record type, 5-5Select Device Type, Viewer, 10-47SETOF data type, 5-25SETOF list, 5-15Sets

using OBED to perform, 20-18setting colors in Viewer window, 10-26severity mapping, 6-8severity propagation, 6-2

topoNodeParents attribute, 6-2topoNodePropagatePeers

attribute, 6-2shadow object, 1-6Show Attributes, browser

SNMP BrowserShow Attributes, 16-9

Simple Network Management Protocol(SNMP), 4-9, 11-1

SNM 2.x compatibility, 2-5SNM agent, 4-10SNM RPC proxy agents, 22-5snmAlarmTraps

Logging to AlarmLog, 6-4SNMP, 4-2, 4-9, 11-1, 20-2

Support for SNMP Version 2, 4-2SNMP Browser

adding agents to a table, 16-24adding new items, 16-22agent field, 16-8arranging table contents, 16-24Attributes Table, 16-9default agent, 16-21


Delete selections, 16-16deleting table contents, 16-24display methods, 16-2Drag and Drop, 16-12MIB information, 16-8Navigator buttons, 16-12New Agents, 16-18Poll Setup window, 16-19Printer field, 16-15Security, 16-2starting, 16-3starting from command line, 16-5Table creation, 16-22Table window, 16-9, 16-10View menu, 16-20

SNMP Browser main window, 16-8SNMP Browser, overview, 16-1SNMP Browser, Viewer, 10-58SNMP daemon

killing, 6-8starting, 6-8

SNMP MIBscompiling, 4-9

SNMP PDM, 2-5, 4-2, 4-9proxy, 4-9request handling, 4-9request received, 4-9response handling, 4-9

SNMP traps, 4-9how they get forwarded to the

MIS, 2-6Solstice EM applications

starting, 2-12Start Time, Data Collector, 12-12Start/Stop Date, Data Collector, 12-12starting

Alarm Manager, 10-58, 15-1from the Viewer

application, 15-1Log Manager, 10-58Log Viewer, 10-59, 14-1the Viewer, 10-5

starting the SNMP Browser, 16-3stateChange

mapped to log record type, 5-5SunNet Manager 2.2 compatibility, 4-9SunNet Manager 2.x schema files, 3-4SunNet Manager traps

how they get forwarded to theMIS, 2-6

superior OI, 4-6

TTable additions, browser, 16-22Table contents, browser, 16-24Table creation, browser, 16-22Table window, browser, 16-9Table window, new (browser), 16-10tables

created by em_log2rdb, 5-17The Discover Function

Overview, 11-1The Monitor Function

Overview, 11-2Time, 11-18timeDomainViolation

mapped to log record type, 5-5Tools applications, 10-43Tools Menu, customizing, 10-72Tools option, Viewer, 10-41Topology Import/Export Tool, 2-10Topology Nodes, 6-1topology-related view, 10-4topoNodeMOSet attribute, 6-1topoNodeSeverity

synchronization with highestuncleared alarm, 6-2

Uufsdump command

to backup database, 2-14ufsrestore command

to restore backup, 2-14user login ID, Access Manager, 9-27

Index-17

User Privileges window, AccessManager, 9-35

User Properties window, AccessManager, 9-30

Vvector mapping

activating in Viewer, 10-23View List window, Viewer, 10-57View menu, Access Manager, 9-32View menu, browser, 16-20View Name, Viewer, 10-53view navigator window in Viewer, 10-10View properties parameters table, 10-68View properties settings, table, 10-22View Properties window parameters

ViewerView Properties, 10-68

ViewerAlarm Manager, 10-58Alarm Severity, 10-29Background Properties, 10-31bitmap (sunraster), 10-32Color Editor, 10-28columns for displaying icons, 10-38configuration file, 10-67Configure, 10-41Configure Device Options, 10-46configuring an icon, 10-60configuring element menus, 10-47creating an icon, 10-60Data Viewer, 10-58Default Activations, 10-71Default Activations window, 10-49default preferences, 10-21Default Properties, 10-40default properties, 10-22deleting objects, 10-18Display, 10-23Display map layers, 10-37Display Object Layers, 10-37Edit options, 10-17executable arguments, 10-43

Filter, 10-33Find Results, 10-52Find window, 10-51Fixed Icon Size button, 10-24Gather

list of matching objects, 10-51specifying object name, 10-52

Gather criteria, 10-52Geographical Map, 10-32Geographical View, 10-65Get or Set request, 10-60Grab Color button, 10-28hierarchical view in, 10-3Icon Label size, 10-25Icon Menu parameters, 10-70Icon Size parameters, 10-23Icon Status Color Source, 10-29icons, 10-10increment of jump, 10-25Layers section, 10-71layout option, 10-19Layout window, 10-38Log Manager, 10-58Log Viewer, 10-59logical layers, 10-35logical view, 10-59managed object categories, 10-2Map, 10-39Map Layers, 10-36, 10-66Maximum Percent, 10-24Minimum Percent, 10-24MIS Manager, 10-59Modify button, 10-23Navigator orientation, 10-23Object Palette, 10-57, 10-63

adding objects to a view, 10-57overview of, 10-1population of, 10-5, 10-59Propagated Alarm Severity, 10-29propagating Alarm Severity, 10-61Request Designer

create a request, 10-55Create button, 10-56modify a request, 10-55Modify button, 10-55

Requests Manager


launching a request, 10-55Requests window, 10-54Reset Properties, 10-39Scale Icon Size, 10-23Select Device Type, 10-47setting colors, 10-26SNMP Browser, 10-58starting, 10-5starting the SNMP Browser, 16-4Status Area, 10-10switching views, 10-62tools, 10-11Tools Menu, 10-72Tools options, 10-41View Name, 10-53View Navigator, 10-62View options, 10-19view properties, 10-19Zoom menu, 10-40Zooming, 10-62

Viewer applications, 10-43Viewer functions, 10-1viewing

detailed log records, 14-12volatile data storage

definition, 23-10

WWrite Attribute Name, Data

Collector, 12-12Write Document Name, Data

Collector, 12-11

XXFILESEARCHPATH environment

variable, 23-1

Zzoom factor

setting in View Properties, 10-25Zoom menu, Viewer, 10-40Zooming, Viewer, 10-62

Copyright 1996 Sun Microsystems Inc., 2550 Garcia Avenue, Mountain View, Californie 94043-1100, U.S.A. Tous droitsréservés.

Ce produit ou document est protégé par un copyright et distribué avec des licences qui en restreignent l’utilisation, la copie,la distribution, et la décompilation. Aucune partie de ce produit ou de sa documentation associée ne peut être reproduite sousaucune forme, par quelque moyen que ce soit, sans l’autorisation préalable et écrite de Sun et de ses bailleurs de licence, s’ily en a.

Des parties de ce produit pourront être dérivées du système UNIX® licencié par Novell, Inc. et du système Berkeley 4.3 BSDlicencié par l’Université de Californie. UNIX est une marque enregistrée aux Etats-Unis et dans d’autres pays et licenciéeexclusivement par X/Open Company Ltd. Le logiciel détenu par des tiers, et qui comprend la technologie relative aux policesde caractères, est protégé par un copyright et licencié par des fournisseurs de Sun.

Sun, Sun Microsystems, le logo Sun, SunSoft, Solstice, Solstice Emterprise Manager, SunNet manager, SunOS, OpenWindows,DeskSet, ONC, SNM, et NFS sont des marques déposées ou enregistrées de Sun Microsystems, Inc. aux Etats-Unis et dansd’autres pays. Toutes les marques SPARC, utilisées sous licence, sont des marques déposées ou enregistrées de SPARCInternational, Inc. aux Etats-Unis et dans d’autres pays. Les produits portant les marques SPARC sont basés sur une architecturedéveloppée par Sun Microsystems, Inc.

Les interfaces d’utilisation graphique OPEN LOOK® et Sun™ ont été développées par Sun Microsystems, Inc. pour sesutilisateurs et licenciés. Sun reconnaît les efforts de pionniers de Xerox pour la recherche et le développement du concept desinterfaces d’utilisation visuelle ou graphique pour l’industrie de l’informatique. Sun détient une licence non exclusive deXerox sur l’interface d’utilisation graphique Xerox, cette licence couvrant aussi les licenciés de Sun qui mettent en placel’interface d’utilisation graphique OPEN LOOK et qui en outre se conforment aux licences écrites de Sun.

Le système X Window est un produit de X Consortium, Inc.

CETTE PUBLICATION EST FOURNIE “EN L’ETAT” SANS GARANTIE D’AUCUNE SORTE, NI EXPRESSE NI IMPLICITE,Y COMPRIS, ET SANS QUE CETTE LISTE NE SOIT LIMITATIVE, DES GARANTIES CONCERNANT LA VALEURMARCHANDE, L’APTITUDE DES PRODUITS A RÉPONDRE A UNE UTILISATION PARTICULIERE, OU LE FAIT QU’ILSNE SOIENT PAS CONTREFAISANTS DE PRODUITS DE TIERS.

Solstice Enterprise Manager Reference Manual · 2550 Garcia Avenue Mountain View, CA 94043 U.S.A....

Documents

Transcript of Solstice Enterprise Manager Reference Manual · 2550 Garcia Avenue Mountain View, CA 94043 U.S.A....