IPMI2_0E4_Markup_061209.pdf

所需积分/C币:10 2019-10-23 15:38:39 2.91MB PDF
4
收藏 收藏
举报

IPMI spec v2.0. Intelligent Platform Management capabilities are a key component in providing enterprise-class management for high-availability systems. Platform status information can be obtained and recovery actions initiated under situations where system management software and normal ‘in-band’ m
Intelligent Platform Management Interface Specification IPMI NON-DISCLOSURE AGREEMENT DO NoT download these files (collectively, the"Confidential Information )until you have carefully read the following terms and conditions. By downloading the confidential Information you agree to the terms of t his Agreement. If you do not wish to so agree, do not download the Confidential Information 1. Confidential Information The confidential, proprietary and trade secret information being disclosed (Confidential ) is that information markedwith a"confidential", "proprietary, or similar legend, and is described as Confidential information: Intelligent Platform Management Interface specificationsecond Generation(v2.0) Intelligent Platform Management Bus Bridge Specification (v1.0), Telligent Chassis Management Bus Bridge Specification(v1.0) CONFIDENTIAL INFORMATION IS PROVIDED SOLELY FOR YOUR INTERNAL EVALUATION AND REVIEW TO DETERMINE WHETHER TO ADOPT THE SPECIFICATIONS BY SIGNING A SEPARATE ADOPTER'S AGREEMENT. THE RECEIVING PARTY IS NOT LICENSED TO IMPLEMENT THE SPECIFICATIONS UNLESS OR UNTIL AN ADOPTER'S AGREEMENT IS EXECUTED DisclosingpartysrepresentativesfordisclosingConfidentialInformationis:FadiZuhayri(fadizuhayri@intel.com) 2. obligations of Receiving Party. The receiving party will maintain the confidentiality of the Confidential Information of information, but no less than a reasonable degree of care under the circumstances the receiving party will not disclose any of the disclosing party,s Confidential Information to employees or to any third parties except to the receiving party's employees, parent company and majority-owned subsidiaries who have a need to know and who agree to abide by nondisclosure terms at least as comprehensive as those set forth herein; provided that the receiving party will be liable for breach any such entity. The receiving party will not make any copiesof Confidential Information received from the disclosing party except as necessary for its employees, parent company and majority-owned subsidiaries with a need to know. Any copies which are made will be identified as belonging to the disclosing party and marked"confidential", "proprietary"or with a similar legend 3. Period of Non-Assertion. Unless a shorter period is indicated below, the disclosing party will not assert any claims for breach of this Agreement or misappropriation of trade secrets aganst the receiving party arising out of the date of receipt of the Confidential Information by the receiving party. However, unless at leasbne of the exceptions et forth in Section 4 below has occurred, the receiving party will continue to treat such Confidential Information as the confidential information of the disclosing party and only disclose any such Confidential Information to third parties under the terms of a non disclosure agreement 4. Termination of obligation of Confidentiality The receiving, party will not be liable for the disclosure of any Confidential Information which is: rightfully in, the public domain other than bya breach of this Agreement of a duty to the disclosing party; (b)rightfully received from a third party without any obligation of confidentiality (c) rightfully known to the receiving party witout any limitation on use or disclosure prior to ts receipt from the disclosing party;(d)independently developed by employees of the receiving party; or(e generally made available to party without restri Inclosure 5. Title. Title or the right to possess Confidential Information as between the parties will remain in the disclosing party 6. No Obligation of Disclosure Termination The disclosing party may terminate this Agreement at any time without cause upon written notice to the other party; provided tha the receiving party s obligations with respect to information disclosed during the term of this Agreement will survive any such termination. The disclosing party may, at any time (a)cease giving Confidential Information to the other party without anyiability, and/or(b)request in writing the return or destruction of all or part of its Confidential Information previously disclosed, and all copies thereof, and the receiving party will promptly comply with such request, and certify in writing its compliance General (a) This Agreement is neither intended to nor will it be construed as creating a joint venture, partnership or other orm of business association between the parties, nor an obligation to buy or sell products using or incorporating he Confidential Information (b) No license under any patent, copyright, trade secret or other intellectual property right is granted to or conferred upon either party in this Agreement or by the transfer of any information by one party to the other pant as contemplated hereunder, either expressly, by implication, inducement, estoppel or otherwise, and that any license under any such intellectual property rights must be express and in writing (c) The failure of either party to enforce any right resulting from breach of any provision of this agreement will not be deemed a waiver of any right relating to a subsequent breach of such provision or of any other right hereunder (d)This Agreement will be governed by the laws of the State of Delaware without rderence to conflict of laws principles. (e)This Agreement constitutes the entire agreement between the parties with respect to the disclosure(s) of Confidential Information described herein, and may not be amended except in a writing signed by a duly authorized representative of the respective parties. Any other agreements between the parties, including non disclosure agreements, will not be affected by this agreement Intelligent Platform Management Interface Specification Table of contents 1. Introduction 11 Audi 1.2 Reference documents 1.3 Conventions and Terminology.……… 1.4 Background - Architectural Goals 1.5 New for IPMi v1.5 1125679 1. 6 New for IPMI v2.0 1.7 IPMI Overview 11 1.7.1 Intelligent Platform Management....... 1.7.2 IPMI Relationship to other Management Standards 1.7.3 Management Controllers and the IPmB 1.74 IPMI Messaging… 1.7.5 Sensor Model 13 1.7.6 System Event Log and Event Messages 14 1.7.7 Sensor Data Records Capabilities Command 1.7.8 Initialization Agent 15 1.7.9S Data Record reposit 15 1.7.10 Private Management busses ···*·· 15 L7.11 FRU Information 1.7.12FRUD 16 1.7.13 Entity Association Records... 16 1.7. 14 Linkage between Events and FRU Information....... ···*·:*4· 1.7. 15 Differentiation and Feature Extensibility 17 1.7. 16 System Interfaces 17 1.7. 17 Other Messaging Interfaces 18 17 18 Serial/Modem Interface 18 1.7.19 LAN Interface 18 1.7. 19a Payloads... 18 1.7.20 Serial Over LAN (SOL).. 9 1.7.21 IPMi and ASF 1.7.22 LAN Alerting 20 1.7.23 Serial/Modem Alerting and Paging……… 20 1.7. 24 Platform Event Filtering(PEF) 20 1.7.25 Call down lists and alert policies 20 1.7.26 Channel Model. Authentication. Sessions. and Users 2 1.7. 27 Standardized Watchdog Timer 1.7. 28 Standardized poh Counter 1. 29 Firmware Firewall .2 1. 7.30 Command and Function Discovery 22 1.7.31 IPMI Hardware Components 1. 7. 32 Configuration Interfaces 22 1. 8 IPMi and BIOS 1.9 System Management Software(SMS) 23 1.10 SMI Handler 24 1.11 Overview of Changes from IPMI v1.0 25 2. Logical Management Device Types…………… 26 3. Baseb。 ard Management controller(BMC)……………………,…,…29 3. 1 Required bMc Functions 32 4. Satellite Controller Required Functions,……,…,…,…,…,…,…,…,…,…,……,………35 5. Message Interface Description 37 Intelligent Platform Management Interface Specification 5.1 Network Function Codes 37 5.2 Completion Codes 5.3 Completion Code requirements 5.3. 1 Response Field Truncation on non-zero Generic Completion Codes 42 5.3.2 Summary of Completion Code Use... 42 5. 4 Sensor owner identification 43 5.5 Software IDS(SWIDs 6 Isolation from Message Content 中·中·“·········· 6. IPMI Messaging Interfaces 45 6. 1 Terminology 45 6.2 Channel Model ……45 6.3 Channel Numbers…. 46 6. 4 Channel Protocol Type 47 6.5 Channel Medium Type 48 6.6 Channel 6.7 Logical Channels... 50 6.8 Channel Privilege levels 50 6.9 Users Password Support 6.9.1 'Anonymous Login Convention ∴51 6.9.2 Anonymous Login Status 6. 10 System Interface Messaging 6. 10.1 BMC Channels and Receive Message Queue 6.10.2 Event Message Buffer 52 6. 11 System Interface Discovery and multiple Interfaces 6.12 IPMI Sessions 53 6.12.1 Session-less Connections 6. 12.2 Single-session Conn 6.12. 3 Multi-session Connections 54 6. 12.4 Per-Message and User Level authentication Disables 6.12.5 Link authentication ·······:···…····:· ∴55 6. 12.6 Summary of Connection Characteristics 55 6. 12.7 Session Activation and IPMI Challenge-Response 56 6. 12.8 Session Sequence Numbers..... 57 6. 12.9 IPMI V1.5 Session Sequence Number Handling 6. 12. 10 IPMI v1. 5 Inbound Session Sequence Number Tracking and Handling 58 6. 12. 1 1 IPMI v1. 5 Out-of-order Packet handling 58 6. 1212 IPMI V1. 5 Outbound Session Sequence Number Tracking and Handling 6. 12 13 IPMI V2.0 RMCP+ Session Sequence Number Handling 6.1214 IPMI V2.0RMCP+ Sliding Window….…, 6. 12.15 Session Inactivity Timeouts.. 59 6. 12a Avoiding"Slot Stealing 60 6. 12 16 Additional Session Specifications and characteristics ··…··…:·:·:::· 6. 13 BMC Message Bridging 6. 13. 1 BMC LUN 10b Routing...... 62 6. 13.2 Send Message Command From System Interface ““·“+“+“ 63 6.13.3 Send message Command with Response Tracking……… 64 6. 13. 4 Bridged Request Example 65 6. 14 Message Size Private Bus Transaction Size requirements 非自非 67 7。 IPMB Interface. E量量国量面日国面■ 71 7. 1 IPMB Access via Master Write-Read command 71 7.2 BMC IPMB LUNS… 71 7.3 Sending Messages to IPMB from System Software 7.4 Sending IPMB M to System Software ……72 7.5 Testing for Event Message Buffer Support 非非 Intelligent Platform Management Interface Specification 8.| CMB Interface,… 8.1 Virtual ICMB Bridge Device 55 8.2 ICMB Bridge Commands in BMC using Channels 75 8.2.1 ICMB Bridging from System Interface to Remote IPMB using Channels 75 8.2.2 ICMB Bridging from Local IPMB to Remote IPMB using Channels 76 9. Keyboard Controller Style(KCs)Interface 79 9.1 KCS Interface/BMC LUNS ………………179 9.2 KCS Interface-BMC Request Message Format 9.3 BMC-KCS Inter face Response Message Format 0 9.4 Logging Events from System Software via KCS Interface 80 9.5 KCS Interface Registers 9.6 KCS Interface Control Codes 9.7 Status Register...... 82 9.7.1 SMS ATN Flag Usage 9.8 Command Register…… …………84 9.9 Data registers 84 9.10 KCS Control codes 9.11 Performing KCS Interface Message Transfers 84 9.12 KCS Communication and Non-communication Interrupts.... 85 9. 13 Physical Interrupt Line Sharing...... 85 9. 14 Additional specifications for the kcs interface 9.15 KCS Flow Diagrams 9. 16 Write Processing Summary 9.17 Read Processing Summary ··············· 9. 18 Error Processing Summary.... 9 19 Interrupting Messages in Progress 92 9.20 KCS Driver Design Recommendations 92 10. SMIC Interface …………………………94 10.1 SMS Transfer streams 10.2 SMIC Communication Register Overview 94 10.3 SMIC/BMC Message Interface Registers 95 10.3.1 Flags register 95 10.3.2 Control/Status Register 96 10.3a Control and Status Codes 96 10.3.3 Data Register... …97 10.4 Performing a single SMIC/BMC Transaction 10.5 Performing a SMIC/ BMC Message Transfer…… 98 10.6 Interrupting Streams in Progress 10.7 Stream Switching 9 10.8 DATA RDY Flag Handling 10.9 SMIC Control and Status Code ranges l00 10.10 SMIC SMS Stream Control Codes 101 10.11 SMIC SMS Stream Status Codes 102 10.12 SMIC Messaging 103 10.13 SMIC/BMC LUNS 103 10.14 SMIC-BMC Request Message Format 10. 15 BMC-SMIC Response Message Format 104 10. 16 Logging Events from System Software via SMIC 11. Block Transfer(BT) nterface…… 105 11. 1 BT Interface-BMC Request Message Format .105 11. 2 BMC-BT Interface Response Message Format 106 11.3 Using the Seq field 106 11.4 Response Expiration Handling…… 107 Intelligent Platform Management Interface Specification 11.5 Logging Events from System Software via BT Interface ∴107 11.6 Host to bMc Interface 108 11.6.1 BT Host Interface Registers l08 11.6.2 BT BMC to Host Buffer(BMC2HOST) 108 1 1.6.3 BT Host to BMC Buffer(HOST2BMC).... 108 11.6.4 BT Control Register (BT CTRL) 109 11.6.5 BT Interrupt Mask Register(INTMAsK) .111 11.7 Communication Protocol 112 118 Host and BMC Busy States…………… 113 11.9 Host Command Power-On/Reset States 113 12. SMBus System Interface(SSF)……………………..…….…………………15 12. 1 Single Threaded Interface 115 12.2 Single-part Write 115 12.3 Multi-part Write 116 12.3. 1 Error conditions for Multi-part Writes. …116 12.4 Single-part Read Transaction 117 12.5 Multi-part Read transactions …117 12.6 Retention of Output data lI8 12.7 SMBAlert Signal Handling........ …119 12.7.1 Enabling/disabling SSIF SMBAlert 119 12.8 Polling for output data 119 12.9 SMBuS NACKs and Error recovery 119 12.10 PEC Handling 119 12. 11 SMBus Timeout and Hang Handling ·*·····:::····:·:·:·····:·········· 120 12.12 Discovering ssiF 120 12 13 SSIF Support Requirements for IPMI vI5-only BMCs 121 12 14 SSIF Support Requirements for IPMI v2.0& Later BMCs...... 121 12. 15 Summary of SMBus Commands values for SSIF 121 12.16 SSIF IPMI Commands 幽自自 12 12.17SSl} Timing…… 122 13. IPMI LAN Interface 画面 n125 13.1 RMCP 126 13.1.1 ASF Messages in RMCP 126 13. 1.2 RMCP Port Numbers 127 13.1.3 RMCP Message Format 128 13.2 Required ASF/RMCP Messages for IPMI-over-LAN 128 13.2.1 RMCP ACK Messages 13.22 RMCP ACK Handling…… 130 13. 2. 3 RMCPIASF Presence Ping Message... 130 13. 2. 4 RMCPiASF Pong Message(Ping Response) ·····:·::················:········ ··中 131 13.3 RMCP+ 131 13.4 BMC Support Requirements for v1.5 and v2.0/RMCP+ Protocols .132 13.4. 1 Session-less Command Support 132 13.5 IPMI Messages Encapsulation Under RMCP 133 13.5.1 RMCPIASF and IPMi Byte Order 133 13.6 Example IPMI over LAN Packet.……… .134 13.7 VLAN Support 137 13.& PMI LAN Message format 137 13.9 LAN Alerting ……138 13. 10 IPMI LAN Configuration 13.10.1 IP and MAC Address Configuration.... 9 13.10.2‘ Teamed’ and fail-0 ver lan channels. 139 13.11 ARP Handling and GratuitouS ARP....….… 139 13. 11.1 OS-Absent problems with ARP Intelligent Platform Management Interface Specification 13. 11.2 Resolving ARP issues. .140 13.11.3 BMC-generated ARPs 141 13. 12 Retaining IP Addresses in a DHCP Environment 14l 13.12.1 Resolving dhCp issues……… 141 13 13 Discovering Support For IPMI over IP Connections .142 13.14 IPMI V1.5 LAN SesSion activation 142 13.15 IPMI V2.0/RMCP+ Session Activation .…14 13 16 RMCP+ Session Termination 145 13.17RMCP+OpenSessionRequest...., ∴.…145 13 18 RMCP+ Open Session response …147 13.19 RAKP Messages l48 13.20 RAKP Message I 148 13.21 RAKP Message 2 .150 13.22 RAKP Message3… ..…151 13.23 RAKP Message 4 .152 13.24 RMCP+ and raKE Message Status Codes 153 13. 25 Differences between v1.5 and v2.0/RMCP- Sessions 13.26 IPMI V2.0 RMCP+ Payload Types 154 13.27 Payloads and Payload Type Numbers …154 13.27.1 IPMI Message Payloads and IPMI Commands……… 155 13.27. 2 OEM Payload Type Handles ∴155 13.27. 3 Payload Type Numbers 156 13.28 Authentication, Integrity, and Confidentiality Algorithm Numbers .156 13. 28. 1 RAKP-HMAC-SHAI Authentication Algorithm...... 157 13.28.1b RAKP-HMAC-SHA256 Authentication Algorithm 157 13. 28.2 RAKP-none Authentication Algorithm .157 13.28.3 RAKP-HMAC-MD5 Authentication Algorithm...... 157 13.28. 4 Integrity algorithms .157 13. 28.5 Confidentiality(Encryption) Algorithms ··中.· 158 13. 29 AES-CBC-128 Encrypted Payload Format...... 13.29. 1 Generating the Initialization Vector 13. 29.2 Encryption with AES .159 13.29. 3 CBC( Cipher Block Chaining)...... 159 13.30 XRC4 Encrypted Payload Format l60 13.30. 1 Generating the xRC4 Initialization Vector 160 13.30.2 Initializing the xRC4 State machines 160 13.31 RMCP+ Authenticated Key-Exchange Protocol(RAKP 161 13. 32 Generating Additional Keying Material 164 13. 33 Setting User Passwords and Keys 丰非:非 164 13. 34 Random Number generation 13.34. 1 Random Number Key ∴165 13. 34.2 Random Number Generator Counters 165 13.34.3 Random Number Generator Operation 16 14.|PMSeriaModemInterface…166 14.1 Serial/Modem Capabilities 166 14.2 Connection modes 166 142.1 Ppp/UDP Proxy Operation…………… 167 14.2.2 Asynchronous Communication Parameters ∴167 14.2.3 Serial Port Sharing l68 14.2.4 Serial port Switching.. 14.2.5 Access modes 169 14.2.6 Console Redirection with Serial Port Sharing 169 14. 2a Detecting Who Answered The Phone 14.2 b Connecting to the BMC…… 170 Intelligent Platform Management Interface Specification 14.2c Connecting to the Console Redirection...... 171 14.2d directing the C lion Aller Power Up/re 171 14.2e Interaction with Microsoft'Headless'Operation 171 14.2f Pre-boot Only Mode 171 4.2g Always Available M 172 14.2 h Shared mode… 172 14.2.7 Serial Port Sharing Access Characteristics .172 14.2.8 Serial Port Sharing Hardware Implementation Notes 174 14.2.9 Connection Mode Auto-detect 175 14.2. 10 Modem-specific options 177 14.2.⊥Mod 177 14.3 Serial/Modem Connection Active 14.3. 1 Serial/ Modem Connection Active Message Parameters .179 14.3.2 Mux Switch Coordination ∴179 14.3.3 Receive During Ping 14.3.4 Application Handling of the Serial/Modem Connection Active Message 179 14. 4 Basic Mode 180 14.4.1 Basic Mode Packet Framing..... 144.2 Data Byte Escaping…………… l80 14.4.3 Message Fields... 181 14.4.4 Message retries 14.45 Packet handshake .182 14.5 PPP/UDP Mode 183 14.5.1 PPP/UDP Mode Sessions 18 14.5.2 PPP Frame Format 183 14.5.3 PPP Frame Implementation Requirements 14.5. 4 Link Control Protocol (LCP)packets .184 14.5.5 Configuration Requests 184 14.5.6 Maximum Receive Unit Handling...... .186 14.5.7 Protocol Field Compression Handling... 186 14.5.8 Address Control Field Compression Handling 186 14.5.9 IPMI/RMCP Message Format in PPP Frame 187 14.5. 10 Example ofIPMI Frame with Field Compression .....188 145.11 Frame Data Encoding .188 14.5.12 Escaping Algorithm …18 14.5.13 Escaped Character handling 188 14.5. 14 Asynch Control Character Maps (aCcm) .189 1 15 IP Network Protocol Negotiation (IPCP) 189 14.5.16 CHAP Operation in PPP Mode 190 14.6 Serial/Modem Callback 191 14.6.1 Callback Control Protocol(CBCP) Support 191 14.6a CBCP Address Type and Dial String Characters 192 14.7 Terminal mode 192 14.7.1 Terminal Mode Versus Basic Mode Differences 193 14.7.2 Terminal Mode Message Format 193 147.3 IPMI Message data ..194 14.7. 4 Terminal Mode IPMI Message Bridging ∴195 14.7. 5 Sending messages to SMs.. 195 14.7.6 Sending Messages to Other Media .............196 147.7 Terminal mode packet handshake …197 147.8 Terminal mode Ascll Text Commands 197 14.7.9 Terminal Mode Text Command and IPMI Message Examples 200 14.8 Terminal Mode Line editing 200 14.9 Terminal Mode Input Restrictions..... 201 14.10 Page Blackout Interval.. 201 Intelligent Platform Management Interface Specification 14.l1 Dial Paging… 201 14.11.1 Alert Strings for Dial Paging ..... 202 14.11.2 Dialing digits 202 14.11.3<Enter> Character(control-M) 202 14.11.4 Long Pause Character(control-L) 202 14.11. 5 Empty(delimiter) Character(FFh) 202 14.11.6Null' Terminator Character (Ooh).. 202 1412 TAP Paging……… 14.12. 1 TAP Escaping( data transparency) 204 14. 12.2 TAP Checksum 204 14.12.3 TAP Response Codes 204 14.12. 4 TAP Page Success Criteria 204 14 13 PPP Alerting 205 15. Serial Over LAN 206 15.1 System Serial Controller Requirements……… 206 15.2 SOL and Serial Port Sharing .206 15.3 SOL Operation Overview. 207 15.4 SOL Security 208 15.5 SOL Sequence Numbers 208 15.6 Flow Control 208 15.7 Bit Rate Handling 208 15.8 Volatile and Non-volatile SOL Configuration Parameters 208 15.9 SOL Payload Data Format 209 15.10 Activating SOL using RMCP+ Authentication ··…··· 211 15. 11 SOL Packet Acknowledge and Retries 12 15. 12 SOL Interaction with Windows. NET EScape Sequences 213 15.13 SOL Payload Activated with Serial Port Sharing 214 16. Event Messages 216 16. 1 Critical Events and System Event Log restrictions 216 16.2 Event Receiver handling of Event messages 17 16.3 IPMB Seq Field use in Event Messages 218 16. 4 Event Status. Event Conditions. and Present state 219 16.5 System Software use of Sensor Scanning bits Entity Info 219 16.6Re- arming…..… 0 16.6.1, Re-arm …220 7. 'Platform Event Filtering(PEF) 222 17.1 Alert policies 222 17.2 Deferred Alerts 非非 222 17. 3 Pef Postpone Timer 222 17.4 PEF Startup Delay 223 17.4. I Last Processed Event Tracking………… ::·:·· 223 17.5 Event Processing When The SeL Is full ∴223 17.6 PEF Actions 224 17.7 Event Filter Table 17.8 Event Data 1 Event Offset mask 27 17.9 Using the Mask and Compare Fields 227 17 10 Mask and Compare Field Examples 227 17. 11 Alert Policy table .228 17.12 Alert Testing. 17.13 Alert Processing…………… 17. 13. 1 Alert Processing after Power loss 17. 13.2 Processing non-Alert Actions after Power Loss 230 17.13.3 Alert Processing when

...展开详情
试读 127P IPMI2_0E4_Markup_061209.pdf
立即下载 低至0.43元/次 身份认证VIP会员低至7折
一个资源只可评论一次,评论内容不能少于5个字
您会向同学/朋友/同事推荐我们的CSDN下载吗?
谢谢参与!您的真实评价是我们改进的动力~
上传资源赚钱or赚积分
最新推荐
IPMI2_0E4_Markup_061209.pdf 10积分/C币 立即下载
1/127
IPMI2_0E4_Markup_061209.pdf第1页
IPMI2_0E4_Markup_061209.pdf第2页
IPMI2_0E4_Markup_061209.pdf第3页
IPMI2_0E4_Markup_061209.pdf第4页
IPMI2_0E4_Markup_061209.pdf第5页
IPMI2_0E4_Markup_061209.pdf第6页
IPMI2_0E4_Markup_061209.pdf第7页
IPMI2_0E4_Markup_061209.pdf第8页
IPMI2_0E4_Markup_061209.pdf第9页
IPMI2_0E4_Markup_061209.pdf第10页
IPMI2_0E4_Markup_061209.pdf第11页
IPMI2_0E4_Markup_061209.pdf第12页
IPMI2_0E4_Markup_061209.pdf第13页
IPMI2_0E4_Markup_061209.pdf第14页
IPMI2_0E4_Markup_061209.pdf第15页
IPMI2_0E4_Markup_061209.pdf第16页
IPMI2_0E4_Markup_061209.pdf第17页
IPMI2_0E4_Markup_061209.pdf第18页
IPMI2_0E4_Markup_061209.pdf第19页
IPMI2_0E4_Markup_061209.pdf第20页

试读结束, 可继续阅读

10积分/C币 立即下载