Use AMISCE tool to update BIOS configuration under linux

Use AMISCE tool to update BIOS configuration under linux

Use AMISCE tool to update BIOS configuration under linux

Test fucntion without change dump file
1.Copy SCELNX_64 to Linux_Flash folder
2.cd Linux_Flash
3#afulnx_64 /MAKEDRV
4.#afulnx_64 /GENDRV [Option 1] /    (ex:./afulnx_64 /GENDRV 2.6.32-71.e16.x86_64 /)
[Option 1]: Specific kernel source 'KERNEL=XXXX' , #uname-r to check
5.#make
6.#SCELNX_64 /o /s nvram.txt /h Hii.db /v /q
7.Reboot to BIOS, change some BIOS configuration
8.Save,boot to linux
9.Boot to OS, cd AMI_SCE folder
10.#SCELNX_64 /i /s nvram.txt  (Restore BIOS to original configuration)
11.Reboot to BIOS, check if configuration is back

--------------------------------------------------------
Change password by modify dump file
Set BIOS Administrator/User password through SCE utility:
0. Set BIOS Administrator/User password and dump nvram file(contain password) with below command
   ./SCELNX_64 /o /c /l list.txt /n nvram.txt /h hii.db
1. Dump nvram file(no password) with below command
   ./SCELNX_64 /o /c /l list.txt /n nvram.txt /h hii.db
2. Edit dumped nvram file to change "Variable Data" about AMITSESetup to set BIOS password. (see nvram.txt in step 0)

No password
Variable Name
AMITSESetup
Variable Data
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
01

Username /password =>是 Admin / 111111 ; User / 111
Variable Name
AMITSESetup
Variable Data
6A 93 87 26 20 BA 6C 4D C7 E0 22 74 7D 07 D8 9A
33 2E 8E C1 E9 54 44 E8 9F 7B FA 0E 55 A2 B0 35
0B C9 66 5C C1 EF 1C 83 6A 93 87 26 20 BA 5D 4D
F6 E0 13 74 7D 07 D8 9A 33 2E 8E C1 E9 54 44 E8
9F 7B FA 0E 55 A2 B0 35 0B C9 66 5C C1 EF 1C 83
00

3. Update nvram file to system using following command.
   ./SCELNX_64 /i /l list.txt /n nvram.txt
4. Reset system and check if BIOS password is set.


Refer:
ftp://12.230.196.227/joel_drivers/BIOS%20Flash%20Utilities/Linux%20Bios%20Flash%20Procedure/UEFI/v2.37/ROMUtils_2.37/LNX/afulnx32/readme_afulnx.txt

The Expert (Short Comedy Sketch)

Which vCenter Server platform should I use - Appliance or Windows? | VMware vSphere Blog - VMware Blogs

Which vCenter Server platform should I use - Appliance or Windows? | VMware vSphere Blog - VMware Blogs

Step 1 – What features are missing?
This used to be a bigger problem than it is today. The only things we are missing at this point with the vCenter Server appliance are Linked Mode, vCenter Server Heartbeat (EoA) and SQL Server support. If you need any of these features, its game over, stick to the vCenter Server on Windows.

Step 2 – Figure out the scale limits.The embedded database that is preinstalled with the vCenter Server appliance will support an inventory size of up to 100 vSphere hosts and/or 3,000 Virtual Machines when sized appropriately. If your scale requirements are higher, is anexternal database an option?  You can use an external database to meet the vCenter maximum scale of up to 1,000 vSphere hosts and/or 10,000 Virtual Machines. However the only external supported database with the vCenter Server appliance is Oracle. If you are a SQL Server shop, the vCenter Server appliance is not for you.

Step 3 – Do you have any operational/environmental/regulatory requirements?
The vCenter Server appliance is delivered on a SUSE distribution, however VMware does not update the OS level patches and hotfixes as they become available, VMware publishes release updates containing the accumulated patches and hotfixes and in the case of vCenter Server, this could be 6 months out (we do deliver critical security patches (ie Heartbleed). Other considerations include 3rd party agents, tweaking Linux settings and removing things aren’t supported. Backup requirements, too, are sometimes a challenge (if, for instance, the database team requires that databases be backed up separately to the virtual appliance).

Step 4 – Using the appliance, today, still requires a certain amount of Linux expertise.
Many customers assume that we’re further down the “lock it down and hide Linux” road than we actually are. I’ve spoken to customers who were excited about moving to the vCenter Server appliance because “we don’t have to worry about the OS, any more.” This may not be true if you get into a troubleshooting scenario or require additional configuration settings.

Step 5 – Migrating to the vCenter Server appliance
Ok so you may have survived the first few steps and ready to adopt the vCenter Server appliance but getting to it maybe more of a challenge. We do not have any migration/data tools available to move your vCenter Server on Windows to the vCenter Server appliance. You will have to deploy a fresh vCenter Server appliance and manually recreate the configuration and manually move the vSphere hosts over to the new vCenter Server appliance. Do you have any auditory requirements? historical data will be lost with the manual migration process and vCOPs will see the vCenter Server appliance as a new vCenter Server environment. This manual process could be eased with the use of PowerCLI but unique to each environment. Using an existing vCenter Server database is not an option.