Good catch on the bidirectional LEDs !LAN0_LED_P
LAN0_LED_L
your panel can have two bidirectional LEDs inside, so the polarity doesn't matter, try it !
Good catch on the bidirectional LEDs !LAN0_LED_P
LAN0_LED_L
your panel can have two bidirectional LEDs inside, so the polarity doesn't matter, try it !
Read a basic book on electronics - something that tells you about LEDs and Anode/Cathode and also a book or web pages on electrical circuits, especially talking about color codes (e.g. Where Do I Start? - SparkFun Learn)
Most switches such as RST/RESET or PWR - will make momentary contact and will not have polarity ( + or - ) - these therefore don't care about how you connect them
LEDs have polarity and are connect as follows The LED positive terminal or + is the Anode is always connected to a + or positive power source. And the LED negative terminal or - or Cathode is always connected to negative polarity / ground / GND.
As fas as wire color codes go - white and green are often used to represent GND or the negative terminal. Blue and red often indicate live or + / positive terminals
NIC1 LED Green => LAN0_LED_L
NIC1 LED Blue => LAN0_LED_P
Boards with 32MB BMC chip cannot be upgraded to BMC 4.0+. Some features (e.g. Redfish API) may not function properly in BIOS 4.01+ when paired with BMC 3.0. If you don't need advanced BMC features it should be fine to stick with 32MB BMC chip and 3.0 BMC.- What are the implication of the limitations with the 32mb/64mb BMC flash chip?
- Why are people sending in the board to get the chip replaced?
- I know you need to stick with BMC v3.0, but what are the limitations compared to v.410?
Thanks
i think to keep the warranty.- Why are people sending in the board to get the chip replaced?
In my experience with most equipment (and if I understood you correctly) warranty counts from purchase (or delivery) date, it is not reset and not starting over from last replacement (which would be relatively easy to exploit turning it into perpetual with orchestrated regular replacements).i think to keep the warranty.
but warranty is void if you soldering yourself on it.In my experience with most equipment (and if I understood you correctly) warranty counts from purchase (or delivery) date, it is not reset and not starting over from last replacement (which would be relatively easy to exploit turning it into perpetual with orchestrated regular replacements).
Ohh, that does makes sense.but warranty is void if you soldering yourself on it.
I was trying to follow your guide but fail every time at Step 3, it always complains about the password "PropertyValueFormatError". Are there any specific password character and length requirements? Is it allowed to use special character like "<" in the password?Enabling Remote BIOS
...
Step 3: So now let's use curl to change the default Redfish account username and password to <new_user> and <new_passwd> (Substitute accordingly)
This should give a HTTP 204 (no content) - but I actually got an error message, the command still worked though. Now when you use the BIOS link to login and use your new username and password, you should be able to see the BIOS settings and even change themCode:curl -k -u 'Administrator:superuser' \ --request PATCH 'https://192.168.0.10/redfish/v1/AccountService/Accounts/1' \ --header 'If-Match: W/"<some_number>"' \ --header 'Content-Type: application/json' \ --data-raw '{"UserName":"<new_user>", "Password":"<new_passwd>" }'
Hope this helps ...
{
"@Message.ExtendedInfo": [
{
"@odata.type": "#Message.v1_0_5.Message",
"Message": "The value of length 14 for the property Password is of a different format than the property can accept.",
"MessageArgs": [
"of length 14",
"Password"
],
"MessageId": "Base.1.0.0.PropertyValueFormatError",
"RelatedProperties": [
"#/Password"
],
"Resolution": "Correct the value for the property in the request body and resubmit the request if the operation failed.",
"Severity": "Warning"
}
],
...
}
Have you tried with a password without special characters? If curl does not work and you are using Windows - try using PostmanI was trying to follow your guide but fail every time at Step 3, it always complains about the password "PropertyValueFormatError". Are there any specific password character and length requirements? Is it allowed to use special character like "<" in the password?
This is not neededI have also noticed in my BIOS settings "Redfish Host Interface" is Disabled and the menu does not allow it to Enable. Could this be a problem and can I enable it?
I tried Postman and used password without special characters. The password setup worked, but wen I go to:Have you tried with a password without special characters? If curl does not work and you are using Windows - try using Postman
Can you share the exact readings after input 0x2e 0x05 0xfd 0x19 0x00 0x03 0xfe?For everyone who is also looking for this. After ~11 days I finally received the answer from Tyan support:
Get/Set PWM Duty
0x2e 0x5 0xfd 0x19 0x00 <PWM ID> <0x00-0x64|0xfe|0xff>
Note:
PWM ID : 0,1,2,3,4,5
0x00-0x64 = 0 -100% duty
0xfe =Get Current PWM Duty
0xff = return to automatic control
For example:
To read current PWM duty cyle:
ipmitool -I lanplus -U <BMC IP> -U root -P <YourPassword> raw 0x2e 0x05 0xfd 0x19 0x00 0x03 0xfe
To set PWM duty cycle to 60 on PWM ID 0
ipmitool -I lanplus -U <BMC IP> -U root -P <YourPassword> raw 0x2e 0x05 0xfd 0x19 0x00 0x00 0x3C
What even more you can control EACH PWM SEPARATELY
You can't basically. Tech support answered that it enabled back in latest BIOS release, but you can't flash it unless you change 32mb chip to 64mb chiphmmm.... I updated my BMC to v3.0 and Bios to latest. Now I have no option to mount media in "remote KVM". Anyone know how I get it back??
BIOS V4.02 is still 32mb.You can't basically. Tech support answered that it enabled back in latest BIOS release, but you can't flash it unless you change 32mb chip to 64mb chip
PSP code ? what operating system ?and displays PSP code 004B, anyone know what this might be?