Brocade Communications Systems 53-1001778-01 manual Overview, Common Information Model CIM

Page 17

 

Chapter

Overview

1

 

 

 

 

In this chapter

Common Information Model (CIM)

1

Brocade SMI-S Initiative

2

Brocade SMI Agent

2

Common Information Model (CIM)

The Common Information Model (CIM) is a conceptual, object-based information model defined by the Distributed Management Task Force (DMTF) for describing management, which is not bound to a particular implementation. This allows for the interchange of management information between management systems and applications.

CIM consists of two parts:

CIM Specification

CIM Schema

The CIM Specification describes the language, naming, metaschema, and mapping techniques to other management models, such as SNMP MIBs and FC-GS. The metaschema is a formal definition of the model that defines the terms used to express the model and their usage and semantics. The elements of the metaschema are classes, properties, and methods. The metaschema also supports indications and associations as types of classes and references as types of properties.

The CIM Schema provides the actual model descriptions. The CIM Schema supplies a set of classes with properties and associations that provide a well-understood conceptual framework within which it is possible to organize the available information about the managed environment. The CIM Schema itself is structured into three distinct layers:

Core Schema

Common Schema

Extension Schema

The Core Schema defines basic classes, such as a managed element or an association. The Common Schema provides a set of foundation classes that can be used as the super-class to describe other devices, such as a system, a device, or a network. The Extension Schema allows users to expand the definitions in the Common Schema to describe specific device types, such as a Brocade FC switch.

The formal definition of the CIM Schema is expressed in a managed object format (MOF) file, which is an ASCII file that can be used as input into a MOF editor, parser, or compiler to generate code for use in a provider or client application.

Web-Based Enterprise Management (WBEM) is a set of management and internet standard technologies to unify management of an enterprise. It includes CIM, CIM Schemas, CIM operations over HTTP, and CIM-XML encoding.

Brocade SMI Agent User’s Guide

1

53-1001778-01

 

Image 17
Contents Brocade SMI Agent Brocade Communications Systems, Incorporated Title Publication number Summary of changes Date Brocade SMI Agent User’s Guide Contents Chapter Brocade SMI Agent Configuration Chapter Mutual Authentication for Clients and Indications Index How this document is organized This chapterSupported hardware and software Text formatting What’s new in this documentDocument conventions Key terms Identifies command syntax examplesOther industry resources Additional informationBrocade resources FT00X0054E9 Getting technical helpSupport@brocade.com Brocade SMI Agent supportDocument feedback Common Information Model CIM OverviewBrocade SMI Agent Brocade SMI-S InitiativeBrocade SMI Agent Brocade SMI Agent User’s Guide Starting the SMI-A Brocade SMI AgentStopping the SMI-A Starting the SMI-A as a serviceStop the Brocade SMI Agent Stopping the SMI-A as a service Service Location Protocol SLP supportSLP on Linux, Solaris, and AIX Slptool commandsStopping SLP on Linux, Solaris, and AIX Starting SLP on Linux, Solaris, and AIXStarting SLP on Windows Installing SLP on WindowsSLP on Windows Connection monitoring Disable Http for security reasonsFor example Enable multi-homed supportAbout the Brocade SMI Agent Configuration Tool Brocade SMI Agent ConfigurationApply Launching the Brocade SMI Agent Configuration Tool Windows Launch the Brocade SMI-A Configuration ToolAdding proxy connections Proxy connectionsReloading provider.xml on fabric segmentation Removing proxy connections Login failure status informationAccess control Login failure status messages Access controlMapping an SMI-A user to a switch user Setting up default SMI-A user mapping SMI Agent security Limitations of SMI-A user-to-switch user mappingConfiguring mutual authentication for clients Mutual authentication setupConfiguring mutual authentication for indications Mutual authentication for indications Configuring Http accessImporting client certificates Http accessExporting server certificates SMI Agent security Configuring user authentication User authentication Encode proxy details Encoding proxy connection detailsConfiguring or removing the SMI Agent as a service SMI Agent service configuration and removalConfiguring the Http and Https ports Port configurationConfigure Http and Https ports Configuring the ARR and eventing ports Configure ARR and eventing portsConfigure ARR and eventing ports Fabric Manager database server configurationConfiguring software locations for firmware download Firmware download software locations configurationFile Path Debugging options for Cimom Debugging and logging options configurationConfiguring debugging options for Cimom Debugging options for the provider Configure debugging options for CimomDynamic Update Configuring debugging options for the providerLogging options for the provider Configuring logging options for providerLog file examples Configure logging optionsCapturing information from the provider cache Capture provider cache informationCollect support information Support information collectionRunning an XML dump XML dumpCollecting support information Configuring the Cimom server Cimom server configurationUncomment the following lines Configuring log file optionsIntroduction Mutual authentication for clientsClient configuration to use client certificates Mutual authentication for indicationsEnabling mutual authentication for clients Enabling mutual authentication for indicationsClient.ind.truststore Clientind.cer Java -classpath SMIAgent/agent/wbem.jar Xmlerror TroubleshootingXmlerror General questions Frequently Asked QuestionsHow do I collect diagnostic data from the Brocade SMI Agent? Does the SMI Agent have support for Https communication? On Linux Type the following command Appendix Open source software used in SMI-ASource Code License Sun Industry Standards Source LicenseDistribution Obligations Inability to Comply DUE to Statute or Regulation Termination IBM Common Public License Grant of Rights Commercial Distribution OpenSLP License GNU Library General Public License Bouncy CastleSun Binary Code License Agreement Public DomainBrocade SMI Agent User’s Guide Supplemental License Terms Brocade SMI Agent User’s Guide Brocade SMI Agent User’s Guide 53-1001778-01 Sun Binary Code License Agreement Index Brocade SMI Agent User’s Guide