Pierre is right, In addition to that basically, assignment of FRU IDs depends on the type of shelf/carrier used, It FRU ID tables can be populated dynamically too. In case of dynamic population the Max FRU Device ID that the board/FRU manages (Managed FRUs) can vary depending on the field-time deployment.

 

Regards

-Gopal

 

 

 


From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Pierre Sangouard
Sent: Tuesday, November 14, 2006 2:08 PM
To: 'Chetan Deshmukh'; [email protected]
Subject: Re: [Openipmi-developer] IPMI Command : Continued.... (attempt 5)

 

Well, it’s all written in the ATCA spec: 5th byte shall always be 0 and 4th byte is “the numerically largest FRU Device ID for the Managed FRUs implemented by this IPMC” so if you have only one FRU (the IPMC itself) it’s going to be 0.

 


From: Chetan Deshmukh [mailto:[EMAIL PROTECTED]
Sent: Tuesday, November 14, 2006 7:37 AM
To: Pierre Sangouard; [email protected]
Subject: RE: [Openipmi-developer] IPMI Command : Continued.... (attempt 5)

 

Thanks Pierre ,
I have good references now.

For  'GET PICMG properties ' command  PICMG 3.0 (ATCA) VD1.0  spec says 4th byte will contain the MAX FRU Device ID and 5th byte will contain FRU device Id.
Why i am getting always getting zero in both the bytes .

Regards
Chetan

Pierre Sangouard <[EMAIL PROTECTED]> wrote:

 

IPMCs:

 

PICMG 3.0 (aka ATCA) R1.0: PICMG Extension Version = 2.0

PICMG 3.0 (aka ATCA) R2.0: PICMG Extension Version = 2.1

PICMG 3.0 (aka ATCA) R2.0 ECN-002: PICMG Extension Version = 2.2

 

MMCs:

AMC.0 R1.0: PICMG Extension Version = 4.0

 

HTH,

Pierre

 

 


From: Chetan Deshmukh [mailto:[EMAIL PROTECTED]
Sent: Monday, November 13, 2006 10:23 AM
To: [email protected]
Subject: [Openipmi-developer] IPMI Command : Continued.... (attempt 5)

 


my last attempt !!


Hello All,
I got the impression that earlier mail in this thread was incomplete and so thought of completing this mail for later reference by someone in need .

 3rd byte of response of command GET PICMG Properties i.e  PICMG extension version field , indicates the version of PICMG extensions implemented by IPM controller.
[7:4] Minor version
[0:3] Major version

So on executing the command
$ipmitool raw 0x2c 0 0
00 02 00 00

It means picmg extension version field is 2.0 that is supported / implemented by the controller.Again  i get the o/p on executing same command on  someother ATCA board :
$ipmitool raw 0x2c 0 0
00 12 00 00

Similarly on executing it on an AMC , i get the response as follows :
$ipmitool raw 0x2c 0 0
00 04 00 00

Does that mean AMC (MMC)  must support/ implement PICMG 4.0 extension version.On PICMG site , i was not able to locate PICMG 4.0 .As per my knowledge, PICMG 3.0 is the latest.Where can i get this 4.0 version spec.One doc named AMC 4.0 i saw on site but it was under construction not able to scan through that.

Is my understanding correct?

Thanks and Regards
Chetan


Sponsored Link

Degrees online in as fast as 1 Yr - MBA, Bachelor's, Master's, Associate - Click now to apply

 

 


Sponsored Link

For just $24.99/mo., Vonage offers unlimited local and long- distance calling. Sign up now.

 

 


Sponsored Link

Mortgage rates near historic lows: $150,000 loan as low as $579/mo. Intro-*Terms

-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Openipmi-developer mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/openipmi-developer

Reply via email to