Dell Poweredge R710: Difference between revisions
| (4 intermediate revisions by the same user not shown) | |||
| Line 3: | Line 3: | ||
= idrac console won't connect = | = idrac console won't connect = | ||
https://gist.github.com/xbb/4fd651c2493ad9284dbcb827dc8886d6 | |||
[[File:Idrac.zip]] | |||
This way worked for me. Note, don't edit the .bat file and put in your ip address and username - just run the bat file and fill in the when prompted | |||
https://github.com/DomiStyle/docker-idrac6#usage a docker image (haven't tested) | |||
== old, doesn't work any more == | |||
Go to Java installation folder. | Go to Java installation folder. | ||
Open {JRE_HOME}\lib\security\java.security -file in text editor. | Open {JRE_HOME}\lib\security\java.security -file in text editor. | ||
Delete or comment out the following | Delete or comment out the following lines | ||
jdk.tls.disabledAlgorithms= | |||
jdk.certpath.disabledAlgorithms= | |||
jdk.jar.disabledAlgorithms= | |||
In java control panel add the ip and port to the exceptions. | |||
I found simply removing RC4 from the list was adequate, this is on an R610 with iDRAC 2.91 and Java 8 Update 181. | I found simply removing RC4 from the list was adequate, this is on an R610 with iDRAC 2.91 and Java 8 Update 181. | ||
| Line 48: | Line 62: | ||
= Buying new hardware = | = Buying new hardware = | ||
www.serverhome.nl | www.serverhome.nl | ||
= Installing OMSA Openmanage Server on esxi = | |||
[https://www.dell.com/support/article/uk/en/ukbsdt1/how10613/how-to-install-openmanage-server-administrator-omsa-on-vmware-to-collect-logs?lang=en#6 instructions here from dell] NB when running the esxcli line, include the full path in the command, not just ./OS....zip! | |||
If you then install in windows, use the hostname = the esxi host, user = root and password. Make sure you check Ignore certificate warnings. | |||
== below solutions should be if you run it as a service not on esxi == | |||
If you are having problems, it could be that user Administrator has not got [https://support.gfi.com/hc/en-us/articles/360012972673-How-do-I-configure-an-user-account-to-have-logon-as-a-service-permissions- logon as a service rights] | |||
Or I restarted the dsm services and was able to login with active directory credentials. | |||
Or | |||
<pre> | |||
I come across with the same problem.. What worked for me was, to use the username: | |||
.\Administrator | |||
which indicates the local domain. | |||
NOTE: If the server where SupportAssist Enterprise is installed is a member of a Windows domain, you must provide the user name in the [Domain\Username] format. For example, MyDomain\MyUsername. You can also use a period [ . ] to indicate the local domain. For example, .\Administrator. | |||
</pre> | |||
Latest revision as of 09:26, 10 September 2019
Dell support page
https://www.dell.com/support/home/us/en/19/product-support/product/poweredge-r710/drivers?lwp=rt
idrac console won't connect
https://gist.github.com/xbb/4fd651c2493ad9284dbcb827dc8886d6
This way worked for me. Note, don't edit the .bat file and put in your ip address and username - just run the bat file and fill in the when prompted
https://github.com/DomiStyle/docker-idrac6#usage a docker image (haven't tested)
old, doesn't work any more
Go to Java installation folder.
Open {JRE_HOME}\lib\security\java.security -file in text editor.
Delete or comment out the following lines
jdk.tls.disabledAlgorithms= jdk.certpath.disabledAlgorithms= jdk.jar.disabledAlgorithms=
In java control panel add the ip and port to the exceptions.
I found simply removing RC4 from the list was adequate, this is on an R610 with iDRAC 2.91 and Java 8 Update 181.
updating BIOS in ESXI
"Enough contiguous physical memory is not available to perform the BIOS update running under this Operating System"
If you run into the above memory limitation on VMWare ESX, the problem is because the console OS available memory is only 272M by default. Please increase the console OS memory to 800M temporarily and perform the FW update. During ESX server boot up please perform the below steps to increase the memory available. 1. While booting, press 'e' or 'Shift-0' on the VMware ESX line (Grub option display screen). 2. Press 'e' again on the 'uppermem=' line and edit uppermem=819200. Press Enter. 3. Press 'e' on the kernel line (Just below the uppermem line). Edit the kernel line with mem=800M and press Enter. 4. Press 'b' to boot with these options. 5. Perform the FW update.
You can enter the shell by enabling it in the web client under hosts or under f2 then troubleshooting options. In the direct console press 'alt-f1' (to return to direct console press alt-f2). Or you can use ssh.
Copy the update file to the storage and don't forget to chmod it 777 before running and then deleting after.
updating idrac in web gui
download the windows version
open the .exe with 7zip
go to the payload directory and extract the firmimg.d6
on the homepage on the right, choose update or in idrac settings, tab update. Browse for and upload the .d6 file. This can take a while. Once it's uploaded you will see the image with version number. Select next. You will then see an updating screen.
Booting through DOS
Using free tool Rufus was easiest to create bootable ms-dos usb (use freedos). Copy the BIOS / unpackaged bios file to this.
Start up the server and select F-11 (UEFI boot manager) whilst booting. Then go to the System Utilities menu and select BIOS Update File Explorer. You should be able to select the usb device and boot into it now. Start the file.
Wait.
Buying new hardware
www.serverhome.nl
Installing OMSA Openmanage Server on esxi
instructions here from dell NB when running the esxcli line, include the full path in the command, not just ./OS....zip!
If you then install in windows, use the hostname = the esxi host, user = root and password. Make sure you check Ignore certificate warnings.
below solutions should be if you run it as a service not on esxi
If you are having problems, it could be that user Administrator has not got logon as a service rights
Or I restarted the dsm services and was able to login with active directory credentials.
Or
I come across with the same problem.. What worked for me was, to use the username:
.\Administrator
which indicates the local domain.
NOTE: If the server where SupportAssist Enterprise is installed is a member of a Windows domain, you must provide the user name in the [Domain\Username] format. For example, MyDomain\MyUsername. You can also use a period [ . ] to indicate the local domain. For example, .\Administrator.