1、ANSI/VITA 38-203 (R208) American National Standard for System Management on VME Secretariat VMEbus International Trade Asociation Aproved January 203, Reafirmed February 208 American National Standards Institute, Inc. VMEbus International Trade Asociation PO Box 19658, Fountain Hils, AZ 85269 PH: 48
2、0-837-7486, FAX: Contact VITA Ofice E-mail: , URL: htp:/ (This page left blank intentionaly.)ANSI/VITA 38-203 (R208) American National Standard for System Management on VME Secretariat VMEbus International Trade Asociation Aproved January 203, Reafirmed 208 American National Standards Institute, Inc
3、. Abstract This standard describes a methodology for using IPMI for System Management of VME systems. American National Standard Aproval of an American National Standard requires verification by ANSI that the requirements for due proces, consensus, and other criteria for aproval have ben met by the
4、standards developer. Consensus is established when, in the judgment of the ANSI Board of Standards Review, substantial agreent has ben reached by directly and materialy afected interests. Substantial agrement eans much more than a simple majority, but not necesarily unaniity. Consensus requires that
5、 al views and objections be considered, and that a concerted efort be made toward their resolution. The use of American National Standards is completely voluntary; their existence does not in any respect preclude anyone, whether he has aproved the standards or not, from anufacturing, marketing, purc
6、hasing, or using products, proceses, or procedures not conforming to the standards. The American National Standards Institute does not develop standards and wil in no circumstances give an interpretation of any American National Standard. Moreover, no person shal have the right or authority to isue
7、an interpretation of an American National Standard in the name of the American National Standard Institute. Requests for interpretations should be adresed to the secretariat or sponsor whose name apears on the title page of this standard. CAUTION NOTICE: This American National Standard may be revise
8、d or withdrawn at any time. The procedures of the American National Standards Institute require that action be taken periodicaly to reafirm, revise, or withdraw this standard. Purchases of American National Standards may receive curent information on al standard by caling or writing the American Nat
9、ional Standards Institute. Published by VMEbus International Trade Asociation PO Box 19658, Fountain Hils, AZ 85269 Copyright 203 by VMEbus International Trade Asociation Al rights reserved. No part of this publication may be reproduced in any form, in an electronic retrieval system or otherwise, wi
10、thout prior writen permision of the publisher. Printed in the United States of America - R1.1 ISBN 1-885731-29-9ANSI/VITA 38 Page 1 TABLE OF CONTENTS 1 Introduction to System Management for VME5 1.1 System Management for VME.5 1.2 Definitions.6 1.3 References.6 1.4 Standard Terminology7 2 System Man
11、agement Pin Assignments.9 2.1. Introduction.9 2.2. VMEbus J1 Pin Assignments.9 2.2.1. J1/P1 Pin Assignments10 2.3. SMB Extension Connector Pin Assignment.11 3 System Management Bus Implementation.12 3.1. Introduction.12 3.2. Compliance with PICMG 2.9.12 3.3. System Management Power12 3.4. Capacitanc
12、e Per VMEbus Slot12 3.5. Secondary IPMI Bus Capacitance12 3.6. SMB Extension Connector.13 Appendix A Glossary of Additional Terms.14 ANSI/VITA 38 Page 2 List of Figures FIGURE 1-1 IPMI CHASIS WIRING DIAGRAM.6 FIGURE 2-1 VMEBUS J1/P1 SYSTEM ANAGEMENT PIN ASIGNMENTS10 FIGURE 2-2 SMB EXTENSION CONECTOR
13、 PIN ASIGNMENT.11 FIGURE 3-1 SMB EXTENSION CONECTOR EXAMPLE.13 ANSI/VITA 38 Page 3 Abstract This standard describes a methodology for using IPMI for System Management of VME systems. The formal name of this standard is System Management for VME Standard. Foreword VME became the industrial bus of cho
14、ice in the 80s with hundreds of manufactures suplying more than a thousand diferent boards to the worldwide market place. Thousands of customers utilized VME for an extremely broad number of aplications. The VME standard extended to 64 bits in 194 and enhanced again in 197 with capabilities to supor
15、t Live Insertion and High Availability. In 198 Intel anounced the availability of the Inteligent Platform Management Interface (IPMI) specification. IPMI describes a hardware independent interface betwen chasis sensors and the operating system. IPI is particularly useful for managing servers and Hig
16、h Availability systems. In 200 IPMI was adapted for use in CompactPCI systems and described in the PICMG 2.9 System Management specification. This standard is based on the PICMG 2.9 System Management specification and describes the aditional requirements for implementing IPMI in a VME system. Michae
17、l Thompson Pentair Electronic Packaging System Management for VME Chair ANSI/VITA 38 Page 4 Working Group Members At the time this standard was completed, the Working Group for this standard had the folowing membership: Name Company Ruth Bary Artesyn Comunication Products Ed Barsoti Fermilab Gorky C
18、hin VISTA Controls Corporation Dany Cohen Sun Microsystems, Inc. Robert Downing Fermilab Melisa Heckman Bustronic Corporation Jing Kwok Dy 4 Systems Inc. Mike MacPherson MITRE Corporation Graham cFarlane olex Incorporated Gregory Novak Motorola Computer Group Steve Pavola SKY Computers, Inc. Elwod P
19、arsons TYCO Electronics Mac Rush Motorola Computer Group John Rynearson VITA Dick Somes Force Computers/Solectron Corp. Bob Sulivan Hybricon Corporation Mark Taylor Bechtel Betis, Inc. Lary Thompson Naval Surface Warfare Center Michael Thompson Pentair Electronic Packaging The ANSI canvas balot grou
20、p consisted of the folowing individuals: Name Company Doug Endo Raytheon Jef Haris Motorola Computer Group Chris Kuebler ACT Technico Mike MacPherson MITRE Elwod Parsons TYCO Electronics Mac Rush Motorola Computer Group John Rynearson VITA Mark Taylor Bechtel Betis, Inc ichael Thompson Pentair Elect
21、ronic Packaging Coments Anyone wishing to provide coments to this standard should email them to the Technical Director of VITA at: . ANSI/VITA 38 Page 5 1 Introduction to System Management for VME 1.1 System Management for VME IPMI (Inteligent Platform Management Interface) is a set of specification
22、s that describe the architecture, adresing, and record formats for system anagement. IPMB (Inteligent Platform Management Bus) is part of IPMI and describes a system anagement bus that is used on a motherboard and in a chasis. ICMB (Inteligent Chasis Management Bus) is also part of IPMI and describe
23、s a bus that can be used to bridge the IPMB bus betwen multiple chasis. The I2C-bus (Inter IC bus) is the physical layer for IPMB. The I2C-bus specification describes the electrical, data transfer, and adresing information for I2C bus. IPMI is not intended to be a replacement for the VMEbus. It is i
24、ntended to suplement the VMEbus and provide a conection betwen the BMC (Baseboard anagement Controler) and Live Insertion Controlers on VME boards, power suplies, fan sped controlers, temperature sensors, and other management devices. A VMEbus System Controler provides the System Clock Driver, Arbit
25、er, IACK Daisy-Chain Driver, and a bus timer. The CPU board that resides in slot one of the VMEbus backplane typicaly includes System Controler functionality. Part of the function of a BMC is to comunicate with the Operating System and exchange system anagement mesages. This standard asumes that the
26、 BMC, System Controler, and CPU are on the same board and are located in slot one of the VMEbus backplane. Since VMEbus suports multiple CPU boards this standard wil refer to the board containing the BMC, CPU, and System Controler as the System Controler Board. The PICMG 2.9 System Management specif
27、ication describes how to implement IPMI in a CompactPCI system. Al of the IPMI specifications can be used as is in a CompactPCI system except for IPMB. PICMG 2.9 defines CompactPCI IPMB pinout and aditional electrical information that is necesary for implementation. This standard describes a methodo
28、logy for implementing IPMI for system anagement in a VME system. The VME implementation of IPMI is based on the PICMG 2.9 CompactPCI System Management specification, and only includes implementation information that is specific to VME. The IPMB implementation for CompactPCI is limited to eight slots
29、. Since the a VMEbus backplane can be up to 21 slots the maximum capacitance per board must be les that that defined in the CompactPCI specification. Figure 1-1 shows a VME chasis with the primary IPMB bus conecting boards in a VMEbus backplane. It also shows the secondary IPMI bus conecting a chasi
30、s environmental monitor and a ICB bridge. The external ICMB cable can be used to conect the IPMB bus betwen multiple chasis. ANSI/VITA 38 Page 6 Figure 1-1 IPMI Chassis Wiring Diagram It is sugested that you read the IPMI and IPMB specifications to get an understanding of the system management bus c
31、apabilities. The PICMG 2.9 CompactPCI System Management specification shows how to adapt IPMI to a backplane environment. 1.2 Definitions Se Apendix A for the new terminology specific to the aded features described in this standard. 1.3 References The folowing publications are used in conjunction wi
32、th this standard. When they are superseded by an aproved revision, that revision shal aply. The folowing standards are available from the VMEbus International Trade Asociation. htp:/ ANSI/VITA 1-1994 VME64 ANSI/VITA 1.1-1997 VE64 Extensions The folowing specification may be downloaded from the Royal
33、 Philips Electronics web page at: htp:/ ANSI/VITA 38 Page 7 I2C Bus Specification The folowing specifications may be downloaded from the Intel Developers web page at: htp:/ IPMI Specification Erata and Clarifications IPMI Specification IPMB Specification ICB Specification Platform Event Trap Specifi
34、cation IPMI Platform Management FRU Information Storage Definition IPB Adres Alocation The folowing specifications are available from the PCI Industrial Computer Manufacturers Group. htp:/ww.picmg.org PICMG 2.0 CompactPCI Specification PICG 2.9 System Management Specification 1.4 Standard Terminolog
35、y To avoid confusion and to make very clear what the requirements for compliance are, many of the paragraphs in this standard are labeled with keywords that indicate the type of information they contain. The keywords are listed below: Rule Recomendation Sugestion Permision Observation Any text not l
36、abeled with one of these keywords describes the System Management structure or operation. It is writen in either a descriptive or a narative style. These keywords are used as folows: Rule .: Rules form the basic framework of this standard. They are sometimes expressed in text form and sometimes in t
37、he form of figures, tables or drawings. All rules shall be followed to ensure compatibility between board and backplane designs. All rules use the “shall“ or “shall not“ words to emphasize the importance of the rule. The “shall“ or “shall not“ words are reserved exclusively for stating rules in this
38、 standard and are not used for any other purpose. Recommendation .: Wherever a recommendation appears, designers would be wise to take the advice given. Doing otherwise might result in poor performance or awkward problems. Recommendations found in this standard are based on experience and are provid
39、ed to designers to speed their traversal of the learning curve. All recommendations use the “should“ or “should not“ words to emphasize the ANSI/VITA 38 Page 8 importance of the recommendation. The “should“ or “should not“ words are reserved exclusively for stating recommendations in this standard a
40、nd are not used for any other purpose. Suggestion .: A suggestion contains advice, which is helpful but not vital. The reader is encouraged to consider the advice before discarding it. Some design decisions that need to be made are difficult until experience has been gained. Suggestions are included
41、 to help a designer who has not yet gained this experience. Permission .: In some cases a rule does not specifically prohibit a certain design approach, but the reader might be left wondering whether that approach might violate the spirit of the rule or whether it might lead to some subtle problem.
42、Permissions reassure the reader that a certain approach is acceptable and will cause no problems. All permissions use the “may“ words to emphasize the importance of the permission. The lower-case “may“ words are reserved exclusively for stating permissions in this standard and are not used for any o
43、ther purpose. Observation .: Observations do not offer any specific advice. They usually follow naturally from what has just been discussed. They spell out the implications of certain rules and bring attention to things that might otherwise be overlooked. They also give the rationale behind certain
44、rules so that the reader understands why the rule must be followed. ANSI/VITA 38 Page 9 2 System Management Pin Asignments 2.1. Introduction Two IPMI System Management buses can be used in a VME system. One bus runs acros the backplane and conects the BC (Baseboard Management Controler) on the Syste
45、m Controler Board to the other VME boards in the backplane. The second IPMI bus conects the BMC on the System Controler Board to chasis resources like power suplies and environmental monitors. Since the second IPMI bus suports non-inteligent sensor devices it includes an ALERT# signal. Observation:
46、2-1 The primary IPMI bus is on row b of the VMEbus J1 backplane connector and can be implemented on both VME64 and VME64x backplanes. The secondary IPMI bus is on row d of the VMEbus J1 backplane connector and can only be implemented on VME64x systems. 2.2. VMEbus J1 Pin Assignments The primary IPMI
47、 System Management bus is routed to al VMEbus J1 backplane conectors on pins J1-b21 and J1-b2. The secondary IPMI System Management bus is routed from the J1 conector in the System Controler Board slot to a 5-pin System anagement bus extension conector on the backplane. A wire harnes mates with this
48、 conector and routes the secondary IPMI System Management bus to chasis resources. Rule 2-1 VMEbus backplanes SHALL bus the IPMB_SCL signal on pin J1-b21 to all slots, and shall bus the IMPB_SDA signal on pin J1-b22 to all slots. Note: These pins were formerly defined as the Serial Bus SERA and SERB
49、 signals in the VME64 Standard. Most VMEbus backplanes have these signals bused. ANSI/VITA 38 Page 10 2.2.1. J1/P1 Pin Assignments Row z Row a Row b Row c Row d Pin Signal Signal Signal Signal Signal Number Mnemonics Mnemonics Mnemonics Mnemonics Mnemonics 1 MPR D0 BSY* D08 VPC 2 GND D01 BCLR* D09 GND 3 MCLK D02 ACFAIL* D10 +V1 4 GND D03 BG0IN* D1 +V2 5 MSD D04 BG0OUT* D12 RsvU 6 GND D05 BG1IN* D13 -V1 7 MMD D06 BG1OUT*
