Language of Management Standards

Transcription

1 Language of Management Standards Julie Schott Cisco, Recently Retired SysDev WG Chair Andrea Westerinen Cisco, DMTF VP of Technology

2 Topics for Discussion Taxonomy of Management Standards Brief Overview of the Standards Questions?

3 Taxonomy of Management Standards Data only MIBs and PIBs, MIF, CIM, SID, SMBIOS, ITU Standards (such as M.3100), XML Schema-based Infrastructure and/or Protocol only (Data independent) Corba, NetConf Data and protocol SNMP/MIBs, RMON, COPS-PR/PIBs, DMI/MIF, CIM- XML/CIM, CMIP and System Management Functions, OASIS Standards (SPML, WSDM, ), ASF, ARM Vendor-defined WMI, JINI, JMX, WFM, IPMI, CLI

4 As Many Standards as Snowflakes

5 Which One Are You?

6 Taxonomy of Management Standards Data only MIBs and PIBs, MIF, CIM, SID, SMBIOS, ITU Standards (such as M.3100), XML Schema-based Infrastructure and/or Protocol only (Data independent) Corba, NetConf Data and protocol SNMP/MIBs, RMON, COPS-PR/PIBs, DMI/MIF, CIM- XML/CIM, CMIP and System Management Functions, OASIS Standards (SPML, WSDM, ), ASF, ARM Vendor-defined WMI, JINI, JMX, WFM, IPMI, CLI

7 MIBs Management Information Base (MIB) Defining Body: Internet Engineering Task Force (IETF), Both standard (IETF RFCs) and proprietary data Information Focus: Internet and intranet environments Data is organized in a Tree Oriented fashion using OIDs (object identifiers) Encoded using ASN.1 - Structure of Management Information (SMIv1 and v2), defined in RFC1155 and 2578

8 Example MIB ciscoflashdevicessupported OBJECT-TYPE SYNTAX Integer32(1..32) ACCESS read-only STATUS mandatory DESCRIPTION "Number of Flash devices supported by the system. " ::= { ciscoflashdevice 1 } ciscoflashdeviceindex OBJECT-TYPE SYNTAX Integer32(1..32) ACCESS not-accessible STATUS mandatory DESCRIPTION "Flash device sequence number to index within the table of initialized flash devices. " ::= { ciscoflashdeviceentry 1 } ciscoflashdevicesize OBJECT-TYPE SYNTAX Integer32 -- Units -- bytes ACCESS read-only STATUS mandatory DESCRIPTION "Total size of the Flash device. For a removable device, the size will be zero if the device has been removed." ::= { ciscoflashdeviceentry 2 }

9 MIBs Pros Interoperable mechanism to access management data Cons No multi-vendor support of standard MIBs (OIDs can only be implemented by a single agent) Application must externally understand the MIB (no ability to query for the MIB definition) Standard MIBs are limited to WAN/LAN management and not consistently adopted Data tends to be specified as read-only Vendor extensions must appear in a new branch Flat structure (Table based)

10 PIBs Policy Information Base Defining Body: IETF Both standard and proprietary data Information Focus Provisioning information, defined as PRCs (PRovisioning Classes) in a module Instances are organized in tables similar to MIBs Encoded using SPPI (Structure of Policy Provisioning Information) A subset of SNMP's Structure of Management Information (SMIv2) for encoding PRCs RFC3159

11 Example PIB qosbaseifcapstable OBJECT-TYPE SYNTAX SEQUENCE OF QosBaseIfCapsEntry PIB-ACCESS notify STATUS current DESCRIPTION "The Base Interface Capability class. This class represents a generic capability supported by a device in the ingress, egress or both directions." ::= { qoscapabilityclasses 1 } qosbaseifcapsentry OBJECT-TYPE SYNTAX QosBaseIfCapsEntry STATUS current DESCRIPTION "An instance of this class describes the qosbaseifcaps class." PIB-INDEX { qosbaseifcapsprid } ::= { qosbaseifcapstable 1 } QosBaseIfCapsEntry ::= SEQUENCE { qosbaseifcapsprid InstanceId, qosbaseifcapsdirection Integer32 }

12 PIB Pros Improvements to SMIv2 including instance pointers, and int64s Cons Few standard PIBs Related to provisioning such as the RAP Framework and DiffServ PIBs Transmitted via COPS-PR which is not widely implemented

13 MIF Management Information Format Defining Body: DMTF, Both standard and proprietary data Standard data available in Master.MIF Information Focus: Desktop / Server Instances or organized in a table fashion Component, Group, Attribute, Row Encoded using the BNF grammar specified in the DMI Specification

14 Example MIF Start Group Name = "ComponentID" Class = "DMTF ComponentID 001" ID = 1 Description = "This group defines the attributes common to all components. This group is required." Pragma = "SNMP: ;" Start Attribute Name = "Manufacturer" ID = 1 Description = "Manufacturer of this system." Access = Read-Only Storage = Common Type = DisplayString(64) Value = "" End Attribute Start Attribute Name = "Product" ID = 2 Description = "Product name for this system." Access = Read-Only Storage = Common Type = DisplayString(64) Value = "" End Attribute End Group

15 MIF Pros MIFs are self describing Multi-vendor support for standard MIF groups Cons Vendor extensions must be defined in a new group Flat structure (Table based) Standard data is limited to the System view Not widely adopted outside the PC client/server environment

16 CIM Common Information Model Defining Body: DMTF Both standard and proprietary data Standard data available as Schema on DMTF web site Proprietary data may be published through WBEMSource initiative Information Focus: Service provider, IT and Enterprise environments Resources and services Object-oriented design (Classes, Properties, Methods) Encoded using Managed Object Format (MOF) BNF grammar in CIM Specification Also rendered in UML

17 Example MOF // ================================================================== // ManagedElement // ================================================================== [Abstract, Version ("2.7.0"), Description ( "ManagedElement is an abstract class that provides a common superclass (or top of the inheritance tree) for the " "non-association classes in the CIM Schema.") ] class CIM_ManagedElement { [MaxLen (64), Description ( "The Caption property is a short textual description (one-line string) of the object.") ] string Caption; [Description ( "The Description property provides a textual description of the object.") ] string Description; [Description ( " A user-friendly name for the object. This property allows each instance to ") ] string ElementName; };

18 CIM Pros Object-oriented structure (integrated extensions) Protocol and repository neutral Allows instance definitions Addresses end-to-end management / all problem domains via a single model (Both breadth and depth of coverage) Builds on and reuses existing standards / Work underway to map and align with TMF s SID Cons Perceived to be difficult to understand Lack of complex data types

19 SID System Information and Data model Defining Body: TeleManagement Forum (TMF) / GB922, Provides standard semantics and data Information Focus Part of the NGOSS strategy (New Generation Operations Systems and Software), based on ISO ODP (Open Distributed Processing) standards Provides the ODP Information viewpoint (information semantics), realizing the ODP Business viewpoint as documented in the Extended Telecom Operations Map etom) Based on the UML Specification (Unified Modeling Lanaguage) from OMG (Object Mgmt Group)

20 Example SID UML comprisedof Product Service 0..n hasproductitems 1..n ProductItem 1 0..n servicerealizedas CustomerFacing Service ResourceFacing Service 1 0..n requires 0..n 0..n resourcerealizedas Resource * Hitchhiker s Guide to SID

21 SID Pros Presents a logical abstraction of the managed environment Includes business aspects of sales and contracts Work underway to map and align with CIM Cons Perceived to be difficult to understand Oriented toward the telecommunications environment Relatively new standard with small number of implementations

22 SMBIOS System Management BIOS Defining Body: DMTF Provides standard data Information Focus Hardware info such as enclosure and processor type Extends the BIOS interface on Intel architecture systems Data encoded in structures/tables in first 1M of memory Each SMBIOS structure has a formatted and an optional unformatted section Formatted section begins with a 4-byte header Remaining data determined by the structure type

23 Example SMBIOS Table Offset Name Length Value Description 00h Type BYTE 0 BIOS Information Indicator 01h Length BYTE Varies 12h + number of BIOS Characteristics Extension Bytes. If no Extension Bytes are used the Length will be 12h. For v2.1 and v2.2 implementations, the length is 13h since one extension byte is defined. For v2.3 and later implementations, the length is at least 14h since two extension bytes are defined. 02h Handle WORD Varies 04h Vendor BYTE STRING String number of the BIOS Vendor s Name 05h BIOS Version BYTE STRING String number of the BIOS Version. This is a free form string that may contain Core and OEM version information.

24 SMBIOS Pros Widely implemented Information standard and easily obtained Cons Limited to static information Only on Intel architecture systems

25 ITU Standards M Series M series standards (M.3100 Generic Network Information Model) Defining Body: International Telecommunication Union (ITU), Provides standard data Information Focus Defines class hierarchy common to telecommunications networks for management of the networks, both resources and services Network element, network and service viewpoints

26 ITU Standards M Series Object-oriented model defined in ASN.1 Based on GDMO X.722 Also based on Definition of Management Information X.721 Also depicted using Entity-Relationship diagrams

27 GDMO Guidelines for Definition of Managed Objects Defining Body: ISO/IEC standard / ITU x.722 Standard description of data Information Focus Information formatted using an OO design Classes defined in an inheritance hierarchy, and instances via containment Encoded using ASN.1

28 Definition of Management Information Alarm record Attribute value change record Discriminator Event forwarding discriminator Event log record Log Log record Object creation record Object deletion record Relationship change record Security alarm report record State change record System Top

29 M.3100 Example E-R Diagram

30 M.3100 Example ASN Network{XE "Network"} network MANAGED OBJECT CLASS DERIVED FROM "Recommendation X.721: 1992":top; CHARACTERIZED BY networkpackage PACKAGE BEHAVIOUR networkdefinition; ATTRIBUTES networkid GET;;; CONDITIONAL PACKAGES userlabelpackage PRESENT IF "an instance supports it"; REGISTERED AS {m3100objectclass 1};

31 ITU Standards M Series Pros Standardization of networking concepts and semantics Object-oriented design Cons Only addresses telecommunications industry Containment hierarchy cumbersome in all scenarios

32 XML Schema-Based extensible Markup Language Defining Body: <Any> Both standard and proprietary data Information Focus Definition of XML tags for the purposes of managing a particular problem domain or vendor product, or conveying domain information Pros Flexible mechanism to define semantics Many supporting tools Cons There are as many possible tags as there are people to define them

33 Taxonomy of Management Standards Data only MIBs and PIBs, MIF, CIM, SID, SMBIOS, ITU Standards (such as M.3100), XML Schema-based Infrastructure and/or Protocol only (Data independent) Corba, NetConf Data and protocol SNMP/MIBs, RMON, COPS-PR/PIBs, DMI/MIF, CIM- XML/CIM, CMIP and System Management Functions, OASIS Standards (SPML, WSDM, ), ASF, ARM Vendor-defined WMI, JINI, JMX, WFM, IPMI, CLI

34 Corba Common Object Request Broker Architecture Much more than a protocol since encodings and services are provided by the Corba infrastructure Defining Body: Object Management Group (OMG), Distributed object computing infrastructure Automates network programming tasks such as object registration, location, and activation; request demultiplexing; framing and error-handling; parameter marshalling and demarshalling; and operation dispatching

35 Corba Request Interfaces Same interface independent of the target Specific to the Interface of the target

36 Corba Interface Definition Language (OMG IDL) defines the types of objects by specifying their interfaces An interface consists of a set of named operations and the parameters to those operations Pros Powerful and flexible infrastructure Could support transmission of CIM or other standard data Cons Complex Not commonly supported outside of high-end application and networking environments Provides infrastructure but no standard semantics

37 NetConf Network Configuration Defining Body: IETF XML based Network Management with focus on configuration Startup, running, candidate and checkpoint (for rollback) configurations Replacement for Expect/Perl scripts which interact with proprietary CLI SOAP or BEEP over TCP/IP

38 NetConf Low-Level Commands Base set set-config, get-config, set-state, get-state Separate candidate supported commit, discard-changes Checkpoint/Rollback supported checkpoint, release-checkpoint, restore Configuration Locking supported lock, unlock Configuration validation supported validate Named Configurations copy-config

39 NetConf Pros Addresses configuration aspects of network devices in vendor independent way Includes concepts of locking and transactions Cons No standard data, just commands Limited in functionality

40 Taxonomy of Management Standards Data only MIBs and PIBs, MIF, CIM, SID, SMBIOS, ITU Standards (such as M.3100), XML Schema-based Infrastructure and/or Protocol only (Data independent) Corba, NetConf Data and protocol SNMP/MIBs, RMON, COPS-PR/PIBs, DMI/MIF, CIM- XML/CIM, CMIP and System Management Functions, OASIS Standards (SPML, WSDM, ), ASF, ARM Vendor-defined WMI, JINI, JMX, WFM, IPMI, CLI

41 SNMP/MIBs Simple Network Management Protocol (SNMP) Defining Body: (IETF) Both standard and proprietary data (MIBs) UDP/IP based

42 SNMP Environment Network control host (manager) Server /Workstation (agent) Network Management Application NME Comm Appl NME Comm Appl Operating System Operating System Router (agent) Network Management Entity Communication Software Operating System

43 SNMP Operations Meta Schema (No support) Data (Get / Set / Multiples) Eventing via Traps Pros Widely adopted by Operating System and Networking communities Cons Standardized at the Network Interface level Interoperability is at the protocol level Data-Centric vs. Task-Oriented

44 RMON Remote Networking Monitoring (RMON) Assumes probes in the network Aggregates the monitoring of individual LAN devices and presents on the LAN as a whole Defining Body: (IETF) Both standard and proprietary data (MIBs) SNMP based

45 COPS-PR/PIBs Common Open Policy Service Defining Body: IETF / RFC2748 Both standard and proprietary data from PIBs TCP/IP based Improvement over SNMP s use of UDP/IP Simple query/request and response/decision protocol Exchanges policy information between a Policy Decision Point (PDP) and its clients (Policy Enforcement Points, PEPs) COPS-Provisioning defined in RFC3084 Never widely implemented

46 DMI Desktop Management Interface (DMI) Defining Body: DMTF Both standard and proprietary data (MIFs) RPC based with DMI defined interfaces

47 DMI Environment Management Application Management Interface Client RPC Support DMI SP Support DMI Service Provider (SP) Component Interface Component Instrumentation Managed Component

48 DMI Operations Meta Schema (Enumerate) Data (Get / Set / Multiples) Eventing via Event standard MIF Group definition Pros Standard System interface and Network interface Standardization of System data Cons Not widely adopted outside the PC client/server environment

49 CIM-XML/CIM CIM encoded in XML using an HTTP transport Part of the Web Based Enterprise Management (WBEM) Initiative Defining Body: DMTF Both standard and proprietary data (defined in MOFs)

50 CIM-XML Environment Client CIM-X ML CIM-XML Protocol Adapter CIM-XML Indication Handler CIM Object Manager (CIMOM) Provider(s) W B E M Server Provider(s) Managed Element

51 CIM-XML Operations Meta Schema (create / get / modify / enumerate) Instance (create / get / modify / enumerate / query) Eventing via CIM Indication Schema definition Pros Object-oriented (Methods and Relationship) Ability to manipulate meta-schema and instances Widely implemented for system and storage management Cons Limited implementation base Interoperability issues between implementations Needs updating to current web technologies

52 CMIP/System Management Functions Common Management Information Protocol Defining Body: ISO-IEC 9596 / ITU X.711 Standard interfaces for MIB data MIBs are a collection of managed objects that contain attributes, exhibit some behaviors, can be created and deleted, and may optionally provide application specific actions that a manager can request System Management Functions defined in ISO series / ITU X.730+ standards Standard semantics for state management, eventing,

53 CMIP Services M-CREATE - Directs an agent to create new instance(s) of a managed object class or attributes within a managed object M-DELETE - Directs an agent to delete existing instances of managed object class(es) or attributes within a set contained in a managed object M-GET - Directs an agent to return attribute values from managed objects M-SET - Directs an agent to change the value of managed object attribute(s) M-ACTION - Directs the agent to cause one or more managed objects to execute an action M-EVENT_REPORT - Issued by an agent to send a notification to manager(s)

54 CMIP Operations and Notifications Operations And Notifications

55 CMIP/System Management Functions Pros Object-oriented design with multiple inheritance First attempt at global semantics Cons Complex and heavy Perceived hard to implement correctly and in small footprint Individual management functions exist in abstraction (for ex, can manage events or the state of anything without understanding the individual classes/instances) Implementations wanted understanding of the complete class definition

56 OASIS Standards Variety of technical committees defining XML languages and frameworks For example, DSML Directory Services SPML Service Provisioning WSDM Web Services Distributed Management WAS Web Application Security (New) Defining Body: OASIS, Standardizes the data and operations for specific tasks Can support multiple bindings (for ex, SPML): SOAP/HTTP File (single file for batch request and response) Uses WSDL to document supported operations

57 SOAP Simple Object Access Protocol Defined by the W3C Specification for RPC-like interactions and message communications using XML and HTTP Three main parts: Message format that uses an envelope, header and body metaphor to wrap XML data Restricted definition of XML data for making strict RPC-like calls, without using a predefined XML schema Binding for SOAP messages to HTTP and extended HTTP May also run over a non-http protocol

58 Web Services for Management (WSDM) Find Manageability Port Service Description Management Management Discovery Discovery Agencies Agencies Publish Any Binding: SOAP/HTTP SOAP Local SNMP* CIMOPs* Service Provider Mgmt. Requester Client Environ Client Interact Service Environment Manageability Service Manageability Port Service Description Manageable Resource

59 ASF Alert Standard Format Defining Body: DMTF UDP/IP based Primarily in the Ethernet controller / Extends to various motherboard and system elements Controller collects information from system components (CPU, chipset, BIOS and sensors) and sends this to a remote server System health information (for ex., POST alerts and heartbeats), environmental notifications, asset security (such as cover tamper and CPU missing ) Primarily for use when the OS is absent or in a lowpower state

60 ASF Protocols Platform Event Trap (PET) to send alerts to the management console SNMP Trap PDU to carry IPMI system information. The alerts cover various low-level system activities and heartbeat Remote Management and Control Protocol (RMCP) to do remote control of the system UDP (User Datagram Protocol) based protocol used for client control functions when a managed client is in an OS-absent state

61 Example ASF RMCP Message Contents Type Offset Value IANA Enterprise Number 4 bytes 00 This field contains the 4-byte value 4542 or 11BEh, the number assigned to ASF by the Internet Assigned Numbers Authority (IANA). The number is transmitted in network byte order. Message Type 1 byte 04h 00h:0Fh Reserved 10h:3Fh Set messages 10h Reset, see page 32 11h Power-up, see page 32 12h Unconditional Power-down, see page 35 13h Power Cycle Reset, see page 32 40h:7Fh Response or Get Response messages 40h Presence Pong, see page 35 41h Capabilities Response, see page 36 42h System State Response, see page 38 43h Open Session Response, see page 39 44h Close Session Response, see page 40 80h:BFh Request or Get messages 80h Presence Ping 81h Capabilities Request 82h System State Request 83h Open Session Request 84h Close Session Request C0h:CFh Authentication/Key Generation messages C0h RAKP Message 1 C1h RAKP Message 2 C2h RAKP Message 3 D0h:FFh Reserved for future definition by this specification Standard RMCP ASF Data

62 ASF Pros Useful when other management mechanisms are not accessible Cons Optimized for client systems Limited in functionality since minimal system resources available

63 ARM Application Response Measurement Defining Body: Open Group, Function calls which can be used to instrument an application or other software for transaction monitoring Provides a way to monitor business transactions, by embedding simple cells in the software which can be captured by an agent supporting the ARM API Oriented toward C/C++ programming

64 Architecture of ARM

65 ARM Function Calls and Standard Data

66 ARM Pros Geared toward application/software management Cons API definition with minimal standard data Not widely implemented

67 Taxonomy of Management Standards Data only MIBs and PIBs, MIF, CIM, SID, SMBIOS, ITU Standards (such as M.3100), XML Schema-based Infrastructure and/or Protocol only (Data independent) Corba, NetConf Data and protocol SNMP/MIBs, RMON, COPS-PR/PIBs, DMI/MIF, CIM- XML/CIM, CMIP and System Management Functions, OASIS Standards (SPML, WSDM, ), ASF, ARM Vendor-defined WMI, JINI, JMX, WFM, IPMI, CLI

68 WMI Windows Management Instrumentation Defining Body: Microsoft Provides both standard (CIM-based) and proprietary data through a DCOM interface Pros Much data is available for the Windows platforms Uniformity of data across the platforms Cons Proprietary interface Different interfaces for drivers providing data, versus other sources of mgmt information

69 JINI Defining Body: Sun Moves data and executables via a Java object Defines leases for recovering from faults Target Environment: Network attach services Pros: Management at the service level vs. device level Cons: Exchange of code and interfaces with no standard semantics

70 JMX Java Management extensions Defining Body: Sun Provides standard APIs, for proprietary data Java API for resources to expose their manageability using a Java Beans-like component model (MBeans) Defines an MBeanServer, allowing instantiation, lookup, and delegation to MBeans registered with it Allows the definition of JMX Adapters to bridge between JMX and other management technologies

71 JMX Pros Supported by most Java middleware vendors (application servers) Part of J2EE and J2SE platforms JMX-CIM bridging techniques exist to create MBeans from CIM MOF (allowing CIM-based attributes, operations and notifications in the MBeans) Cons Java specific No consistent data semantics Not widely implemented outside of application server environments

72 WFM Wired For Management Defining Body: Intel Collection of standards outlining minimum level of management capabilities for all desktop, mobile, and server systems Based on ACPI, DMI, CIM/WBEM, CIM/WMI, SNMP, SES/SIS, SMBIOS, PXE, etc. Pros: Reduced Cost of Ownership by answering the what question for system vendors and the component vendor Cons: Limited to single systems For Intel architecture systems

73 IPMI Intelligent Platform Management Interface (IPMI) Defining Bodies: Intel, HP, NEC, and Dell Defines a standardized, abstracted, message-based interface for platform management hardware Defines standardized records for describing platform management devices and their characteristics Independent of the management software Target Environment: Baseboard / Motherboard environments

74 IPMI and CIM Management Applications CIM CIM Object Manager CIM Object Manager IPMI Instrumentation Provider IPMI I/F Code In-Band IPMI H/W I/F Baseboard Mgmt. Controller and monitoring h/w OOB I/F IPMI Messages Common interface for in-band and out-of of-band platform management Proxy Provider IPMI I/F Code Out-Of-Band Network, Serial, Modem, Inter-Chassis Mgmt Bus

75 IPMI Pros Widely implemented Information standard and easily obtained Cons Only on Intel architecture systems

76 CLI Command Line Interface Defining Body: Various companies Proprietary data Transmitted via telnet or XML tagged Pros All data and operations available to the operator Cons Complex Variable across products Processed via screen scraping

77 Which One Are You? (Revisited)

78 Discussion Points Other taxonomies are possible such as whether the processing environment assumes manageragent, client-server, or peer to peer interactions Other standards and references to note: Storage Management Initiative, SMI-S IT Infrastructure Library, ITIL or

79 Questions?