Hello EveryOne

I had a problem with SNMP with ILO 4 (Insight Agent), I mean that The SNMP  was implemented in our Blade servers (HP Blade SYstem C7000), but some servers display this error "Error making call: call=snmp_settings; error=500; message=JS_ERR_FAILURE; details=CONFIG_READ_ERROR" and when I see the "Administration -> management" session i got this erreur "Error making call: snmpv3_settings", and I'am not able to modify settings in "Access settings"  session,

so, please help me to complete this action.

Thanks

Hi Mr,

suse 12 sp1 don't install on the server HP PROLIANT SL 4540 gen8.

i have upgraded service pack for proliant for have the support of the suse 12 sp1 os.

Nevertheless, during the os install the ssd disk connected to controller b120i are viewed like simple disk not like raid 1.

So, then the install is finished, the server don't boot on the install disk.

it 's similarly with a disk attached with controller h220.

what is the install procedure for suse os ?

i'm precise that the same problem with other os.

thanks

During boot, I get fllowing log at /var/log/messages.

What does this log mean?

May 24 17:27:49 triton kernel: EFI v2.40 by HP

May 24 17:27:49 triton kernel: SMBIOS=0x7a6c9000  ACPI=0x7bfea000  ACPI 2.0=0x7bfea014

May 24 17:27:49 triton kernel: EFI: mem00: type=7, attr=0xf, range=[0x0000000000000000-0x0000000000056000) (0MB)

May 24 17:27:49 triton kernel: EFI: mem01: type=2, attr=0xf, range=[0x0000000000056000-0x0000000000058000) (0MB)

May 24 17:27:49 triton kernel: EFI: mem02: type=0, attr=0xf, range=[0x0000000000058000-0x0000000000059000) (0MB)

May 24 17:27:49 triton kernel: EFI: mem03: type=7, attr=0xf, range=[0x0000000000059000-0x000000000009e000) (0MB)

May 24 17:27:49 triton kernel: EFI: mem04: type=0, attr=0xf, range=[0x000000000009e000-0x00000000000a0000) (0MB)

May 24 17:27:49 triton kernel: EFI: mem05: type=7, attr=0xf, range=[0x0000000000100000-0x000000004a615000) (1189MB)

May 24 17:27:49 triton kernel: EFI: mem06: type=4, attr=0xf, range=[0x000000004a615000-0x000000004a695000) (0MB)

May 24 17:27:49 triton kernel: EFI: mem07: type=7, attr=0xf, range=[0x000000004a695000-0x0000000066cc8000) (454MB)

May 24 17:27:49 triton kernel: EFI: mem08: type=2, attr=0xf, range=[0x0000000066cc8000-0x0000000069696000) (41MB)

May 24 17:27:49 triton kernel: EFI: mem09: type=7, attr=0xf, range=[0x0000000069696000-0x00000000696e2000) (0MB)

May 24 17:27:49 triton kernel: EFI: mem10: type=2, attr=0xf, range=[0x00000000696e2000-0x0000000069d3c000) (6MB)

May 24 17:27:49 triton kernel: EFI: mem11: type=1, attr=0xf, range=[0x0000000069d3c000-0x0000000069d7d000) (0MB)

May 24 17:27:49 triton kernel: EFI: mem12: type=2, attr=0xf, range=[0x0000000069d7d000-0x0000000069dbc000) (0MB)

May 24 17:27:49 triton kernel: EFI: mem13: type=4, attr=0xf, range=[0x0000000069dbc000-0x0000000069e4d000) (0MB)

May 24 17:27:49 triton kernel: EFI: mem14: type=2, attr=0xf, range=[0x0000000069e4d000-0x0000000069e65000) (0MB)

May 24 17:27:49 triton kernel: EFI: mem15: type=4, attr=0xf, range=[0x0000000069e65000-0x0000000069e66000) (0MB)

May 24 17:27:49 triton kernel: EFI: mem16: type=2, attr=0xf, range=[0x0000000069e66000-0x0000000069e68000) (0MB)

May 24 17:27:49 triton kernel: EFI: mem17: type=4, attr=0xf, range=[0x0000000069e68000-0x0000000069e69000) (0MB)

May 24 17:27:49 triton kernel: EFI: mem18: type=2, attr=0xf, range=[0x0000000069e69000-0x0000000069e6c000) (0MB)

May 24 17:27:49 triton kernel: EFI: mem19: type=4, attr=0xf, range=[0x0000000069e6c000-0x0000000069e73000) (0MB)

May 24 17:27:49 triton kernel: EFI: mem20: type=2, attr=0xf, range=[0x0000000069e73000-0x0000000069e76000) (0MB)

May 24 17:27:49 triton kernel: EFI: mem21: type=4, attr=0xf, range=[0x0000000069e76000-0x0000000069e78000) (0MB)

May 24 17:27:49 triton kernel: EFI: mem22: type=2, attr=0xf, range=[0x0000000069e78000-0x0000000069e79000) (0MB)

May 24 17:27:49 triton kernel: EFI: mem23: type=4, attr=0xf, range=[0x0000000069e79000-0x000000006b3e4000) (21MB)

May 24 17:27:49 triton kernel: EFI: mem24: type=5, attr=0x800000000000000f, range=[0x000000006b3e4000-0x000000006b46e000) (0MB)

May 24 17:27:49 triton kernel: EFI: mem25: type=4, attr=0xf, range=[0x000000006b46e000-0x000000006b4b5000) (0MB)

May 24 17:27:49 triton kernel: EFI: mem26: type=3, attr=0xf, range=[0x000000006b4b5000-0x000000006b4cb000) (0MB)

May 24 17:27:49 triton kernel: EFI: mem27: type=4, attr=0xf, range=[0x000000006b4cb000-0x000000006b568000) (0MB)

May 24 17:27:49 triton kernel: EFI: mem28: type=3, attr=0xf, range=[0x000000006b568000-0x000000006b5e2000) (0MB)

May 24 17:27:49 triton kernel: EFI: mem29: type=4, attr=0xf, range=[0x000000006b5e2000-0x000000006b666000) (0MB)

May 24 17:27:49 triton kernel: EFI: mem30: type=3, attr=0xf, range=[0x000000006b666000-0x000000006b70d000) (0MB)

May 24 17:27:49 triton kernel: EFI: mem31: type=4, attr=0xf, range=[0x000000006b70d000-0x000000006b732000) (0MB)

May 24 17:27:49 triton kernel: EFI: mem32: type=3, attr=0xf, range=[0x000000006b732000-0x000000006b759000) (0MB)

May 24 17:27:49 triton kernel: EFI: mem33: type=4, attr=0xf, range=[0x000000006b759000-0x000000006b75f000) (0MB)

May 24 17:27:49 triton kernel: EFI: mem34: type=3, attr=0xf, range=[0x000000006b75f000-0x000000006b793000) (0MB)

May 24 17:27:49 triton kernel: EFI: mem35: type=4, attr=0xf, range=[0x000000006b793000-0x000000006b799000) (0MB)

May 24 17:27:49 triton kernel: EFI: mem36: type=3, attr=0xf, range=[0x000000006b799000-0x000000006b7ac000) (0MB)

May 24 17:27:49 triton kernel: EFI: mem37: type=4, attr=0xf, range=[0x000000006b7ac000-0x000000006b7b3000) (0MB)

May 24 17:27:49 triton kernel: EFI: mem38: type=3, attr=0xf, range=[0x000000006b7b3000-0x000000006b7c0000) (0MB)

May 24 17:27:49 triton kernel: EFI: mem39: type=4, attr=0xf, range=[0x000000006b7c0000-0x000000006b7c4000) (0MB)

May 24 17:27:49 triton kernel: EFI: mem40: type=3, attr=0xf, range=[0x000000006b7c4000-0x000000006b7d6000) (0MB)

May 24 17:27:49 triton kernel: EFI: mem41: type=4, attr=0xf, range=[0x000000006b7d6000-0x000000006b7f2000) (0MB)

May 24 17:27:49 triton kernel: EFI: mem42: type=3, attr=0xf, range=[0x000000006b7f2000-0x000000006b84f000) (0MB)

May 24 17:27:49 triton kernel: EFI: mem43: type=4, attr=0xf, range=[0x000000006b84f000-0x000000006b857000) (0MB)

May 24 17:27:49 triton kernel: EFI: mem44: type=3, attr=0xf, range=[0x000000006b857000-0x000000006b8a3000) (0MB)

May 24 17:27:49 triton kernel: EFI: mem45: type=4, attr=0xf, range=[0x000000006b8a3000-0x000000006b8ff000) (0MB)

May 24 17:27:49 triton kernel: EFI: mem46: type=3, attr=0xf, range=[0x000000006b8ff000-0x000000006b912000) (0MB)

May 24 17:27:49 triton kernel: EFI: mem47: type=4, attr=0xf, range=[0x000000006b912000-0x000000006b913000) (0MB)

May 24 17:27:49 triton kernel: EFI: mem48: type=3, attr=0xf, range=[0x000000006b913000-0x000000006b92c000) (0MB)

May 24 17:27:49 triton kernel: EFI: mem49: type=4, attr=0xf, range=[0x000000006b92c000-0x000000006b92e000) (0MB)

May 24 17:27:49 triton kernel: EFI: mem50: type=3, attr=0xf, range=[0x000000006b92e000-0x000000006b933000) (0MB)

May 24 17:27:49 triton kernel: EFI: mem51: type=4, attr=0xf, range=[0x000000006b933000-0x000000006b935000) (0MB)

May 24 17:27:49 triton kernel: EFI: mem52: type=3, attr=0xf, range=[0x000000006b935000-0x000000006b93d000) (0MB)

May 24 17:27:49 triton kernel: EFI: mem53: type=4, attr=0xf, range=[0x000000006b93d000-0x000000006b93e000) (0MB)

May 24 17:27:49 triton kernel: EFI: mem54: type=3, attr=0xf, range=[0x000000006b93e000-0x000000006b94c000) (0MB)

May 24 17:27:49 triton kernel: EFI: mem55: type=4, attr=0xf, range=[0x000000006b94c000-0x000000006b94d000) (0MB)

May 24 17:27:49 triton kernel: EFI: mem56: type=3, attr=0xf, range=[0x000000006b94d000-0x000000006ba09000) (0MB)

May 24 17:27:49 triton kernel: EFI: mem57: type=4, attr=0xf, range=[0x000000006ba09000-0x000000006ba13000) (0MB)

May 24 17:27:49 triton kernel: EFI: mem58: type=3, attr=0xf, range=[0x000000006ba13000-0x000000006ba21000) (0MB)

May 24 17:27:49 triton kernel: EFI: mem59: type=4, attr=0xf, range=[0x000000006ba21000-0x000000006ba23000) (0MB)

May 24 17:27:49 triton kernel: EFI: mem60: type=3, attr=0xf, range=[0x000000006ba23000-0x000000006ba4a000) (0MB)

May 24 17:27:49 triton kernel: EFI: mem61: type=4, attr=0xf, range=[0x000000006ba4a000-0x000000006ba54000) (0MB)

May 24 17:27:49 triton kernel: EFI: mem62: type=3, attr=0xf, range=[0x000000006ba54000-0x000000006ba58000) (0MB)

May 24 17:27:49 triton kernel: EFI: mem63: type=4, attr=0xf, range=[0x000000006ba58000-0x000000006ba5c000) (0MB)

May 24 17:27:49 triton kernel: EFI: mem64: type=3, attr=0xf, range=[0x000000006ba5c000-0x000000006bb50000) (0MB)

May 24 17:27:49 triton kernel: EFI: mem65: type=4, attr=0xf, range=[0x000000006bb50000-0x000000006bb59000) (0MB)

May 24 17:27:49 triton kernel: EFI: mem66: type=3, attr=0xf, range=[0x000000006bb59000-0x000000006bb7b000) (0MB)

May 24 17:27:49 triton kernel: EFI: mem67: type=4, attr=0xf, range=[0x000000006bb7b000-0x000000006bb7c000) (0MB)

May 24 17:27:49 triton kernel: EFI: mem68: type=3, attr=0xf, range=[0x000000006bb7c000-0x000000006bbb8000) (0MB)

May 24 17:27:49 triton kernel: EFI: mem69: type=4, attr=0xf, range=[0x000000006bbb8000-0x000000006bbbe000) (0MB)

May 24 17:27:49 triton kernel: EFI: mem70: type=3, attr=0xf, range=[0x000000006bbbe000-0x000000006bbc2000) (0MB)

May 24 17:27:49 triton kernel: EFI: mem71: type=4, attr=0xf, range=[0x000000006bbc2000-0x000000006bbc4000) (0MB)

May 24 17:27:49 triton kernel: EFI: mem72: type=3, attr=0xf, range=[0x000000006bbc4000-0x000000006bbcb000) (0MB)

May 24 17:27:49 triton kernel: EFI: mem73: type=4, attr=0xf, range=[0x000000006bbcb000-0x000000006bbd3000) (0MB)

May 24 17:27:49 triton kernel: EFI: mem74: type=3, attr=0xf, range=[0x000000006bbd3000-0x000000006bc49000) (0MB)

May 24 17:27:49 triton kernel: EFI: mem75: type=4, attr=0xf, range=[0x000000006bc49000-0x000000006bc4a000) (0MB)

May 24 17:27:49 triton kernel: EFI: mem76: type=3, attr=0xf, range=[0x000000006bc4a000-0x000000006bc4d000) (0MB)

May 24 17:27:49 triton kernel: EFI: mem77: type=4, attr=0xf, range=[0x000000006bc4d000-0x000000006bc56000) (0MB)

May 24 17:27:49 triton kernel: EFI: mem78: type=3, attr=0xf, range=[0x000000006bc56000-0x000000006bc68000) (0MB)

May 24 17:27:49 triton kernel: EFI: mem79: type=4, attr=0xf, range=[0x000000006bc68000-0x000000006bc69000) (0MB)

May 24 17:27:49 triton kernel: EFI: mem80: type=3, attr=0xf, range=[0x000000006bc69000-0x000000006bc6c000) (0MB)

May 24 17:27:49 triton kernel: EFI: mem81: type=4, attr=0xf, range=[0x000000006bc6c000-0x000000006bc6d000) (0MB)

May 24 17:27:49 triton kernel: EFI: mem82: type=3, attr=0xf, range=[0x000000006bc6d000-0x000000006bc8f000) (0MB)

May 24 17:27:49 triton kernel: EFI: mem83: type=4, attr=0xf, range=[0x000000006bc8f000-0x000000006bc9c000) (0MB)

May 24 17:27:49 triton kernel: EFI: mem84: type=3, attr=0xf, range=[0x000000006bc9c000-0x000000006bd0c000) (0MB)

May 24 17:27:49 triton kernel: EFI: mem85: type=4, attr=0xf, range=[0x000000006bd0c000-0x000000006bd14000) (0MB)

May 24 17:27:49 triton kernel: EFI: mem86: type=3, attr=0xf, range=[0x000000006bd14000-0x000000006bd77000) (0MB)

May 24 17:27:49 triton kernel: EFI: mem87: type=4, attr=0xf, range=[0x000000006bd77000-0x000000006bd84000) (0MB)

May 24 17:27:49 triton kernel: EFI: mem88: type=3, attr=0xf, range=[0x000000006bd84000-0x000000006bd8f000) (0MB)

May 24 17:27:49 triton kernel: EFI: mem89: type=4, attr=0xf, range=[0x000000006bd8f000-0x000000006bd92000) (0MB)

May 24 17:27:49 triton kernel: EFI: mem90: type=2, attr=0xf, range=[0x000000006bd92000-0x000000006bd93000) (0MB)

May 24 17:27:49 triton kernel: EFI: mem91: type=4, attr=0xf, range=[0x000000006bd93000-0x000000006bda5000) (0MB)

May 24 17:27:49 triton kernel: EFI: mem92: type=2, attr=0xf, range=[0x000000006bda5000-0x000000006bda7000) (0MB)

May 24 17:27:49 triton kernel: EFI: mem93: type=4, attr=0xf, range=[0x000000006bda7000-0x000000006bdaa000) (0MB)

May 24 17:27:49 triton kernel: EFI: mem94: type=3, attr=0xf, range=[0x000000006bdaa000-0x000000006bdaf000) (0MB)

May 24 17:27:49 triton kernel: EFI: mem95: type=4, attr=0xf, range=[0x000000006bdaf000-0x000000006bdb0000) (0MB)

May 24 17:27:49 triton kernel: EFI: mem96: type=3, attr=0xf, range=[0x000000006bdb0000-0x000000006bde0000) (0MB)

May 24 17:27:49 triton kernel: EFI: mem97: type=4, attr=0xf, range=[0x000000006bde0000-0x000000006bdee000) (0MB)

May 24 17:27:49 triton kernel: EFI: mem98: type=3, attr=0xf, range=[0x000000006bdee000-0x000000006bdf6000) (0MB)

May 24 17:27:49 triton kernel: EFI: mem99: type=0, attr=0xf, range=[0x000000006bdf6000-0x0000000073df6000) (128MB)

May 24 17:27:49 triton kernel: EFI: mem100: type=4, attr=0xf, range=[0x0000000073df6000-0x0000000073eb0000) (0MB)

May 24 17:27:49 triton kernel: EFI: mem101: type=3, attr=0xf, range=[0x0000000073eb0000-0x0000000073eca000) (0MB)

May 24 17:27:49 triton kernel: EFI: mem102: type=4, attr=0xf, range=[0x0000000073eca000-0x00000000741bf000) (2MB)

May 24 17:27:49 triton kernel: EFI: mem103: type=3, attr=0xf, range=[0x00000000741bf000-0x00000000741c4000) (0MB)

May 24 17:27:49 triton kernel: EFI: mem104: type=4, attr=0xf, range=[0x00000000741c4000-0x00000000741d4000) (0MB)

May 24 17:27:49 triton kernel: EFI: mem105: type=3, attr=0xf, range=[0x00000000741d4000-0x00000000741d8000) (0MB)

May 24 17:27:49 triton kernel: EFI: mem106: type=4, attr=0xf, range=[0x00000000741d8000-0x00000000741f3000) (0MB)

May 24 17:27:49 triton kernel: EFI: mem107: type=3, attr=0xf, range=[0x00000000741f3000-0x00000000741f6000) (0MB)

May 24 17:27:49 triton kernel: EFI: mem108: type=4, attr=0xf, range=[0x00000000741f6000-0x00000000742ed000) (0MB)

May 24 17:27:49 triton kernel: EFI: mem109: type=3, attr=0xf, range=[0x00000000742ed000-0x00000000742f0000) (0MB)

May 24 17:27:49 triton kernel: EFI: mem110: type=4, attr=0xf, range=[0x00000000742f0000-0x0000000074315000) (0MB)

May 24 17:27:49 triton kernel: EFI: mem111: type=3, attr=0xf, range=[0x0000000074315000-0x0000000074338000) (0MB)

May 24 17:27:49 triton kernel: EFI: mem112: type=4, attr=0xf, range=[0x0000000074338000-0x000000007433a000) (0MB)

May 24 17:27:49 triton kernel: EFI: mem113: type=3, attr=0xf, range=[0x000000007433a000-0x0000000074562000) (2MB)

May 24 17:27:49 triton kernel: EFI: mem114: type=4, attr=0xf, range=[0x0000000074562000-0x0000000074568000) (0MB)

May 24 17:27:49 triton kernel: EFI: mem115: type=3, attr=0xf, range=[0x0000000074568000-0x000000007456e000) (0MB)

May 24 17:27:49 triton kernel: EFI: mem116: type=4, attr=0xf, range=[0x000000007456e000-0x000000007476e000) (2MB)

May 24 17:27:49 triton kernel: EFI: mem117: type=3, attr=0xf, range=[0x000000007476e000-0x00000000747d2000) (0MB)

May 24 17:27:49 triton kernel: EFI: mem118: type=4, attr=0xf, range=[0x00000000747d2000-0x00000000747e2000) (0MB)

May 24 17:27:49 triton kernel: EFI: mem119: type=3, attr=0xf, range=[0x00000000747e2000-0x000000007484d000) (0MB)

May 24 17:27:49 triton kernel: EFI: mem120: type=4, attr=0xf, range=[0x000000007484d000-0x0000000074852000) (0MB)

May 24 17:27:49 triton kernel: EFI: mem121: type=3, attr=0xf, range=[0x0000000074852000-0x0000000074971000) (1MB)

May 24 17:27:49 triton kernel: EFI: mem122: type=4, attr=0xf, range=[0x0000000074971000-0x0000000074f9d000) (6MB)

May 24 17:27:49 triton kernel: EFI: mem123: type=3, attr=0xf, range=[0x0000000074f9d000-0x0000000074fa5000) (0MB)

May 24 17:27:49 triton kernel: EFI: mem124: type=4, attr=0xf, range=[0x0000000074fa5000-0x0000000074fa9000) (0MB)

May 24 17:27:49 triton kernel: EFI: mem125: type=3, attr=0xf, range=[0x0000000074fa9000-0x0000000074fb5000) (0MB)

May 24 17:27:49 triton kernel: EFI: mem126: type=4, attr=0xf, range=[0x0000000074fb5000-0x0000000074fb6000) (0MB)

May 24 17:27:49 triton kernel: EFI: mem127: type=3, attr=0xf, range=[0x0000000074fb6000-0x0000000074fbc000) (0MB)

May 24 17:27:49 triton kernel: EFI: mem128: type=4, attr=0xf, range=[0x0000000074fbc000-0x0000000074fbd000) (0MB)

May 24 17:27:49 triton kernel: EFI: mem129: type=3, attr=0xf, range=[0x0000000074fbd000-0x0000000074fc9000) (0MB)

May 24 17:27:49 triton kernel: EFI: mem130: type=4, attr=0xf, range=[0x0000000074fc9000-0x0000000074fcd000) (0MB)

May 24 17:27:49 triton kernel: EFI: mem131: type=3, attr=0xf, range=[0x0000000074fcd000-0x0000000074ff6000) (0MB)

May 24 17:27:49 triton kernel: EFI: mem132: type=4, attr=0xf, range=[0x0000000074ff6000-0x0000000074ffa000) (0MB)

May 24 17:27:49 triton kernel: EFI: mem133: type=3, attr=0xf, range=[0x0000000074ffa000-0x0000000075008000) (0MB)

May 24 17:27:49 triton kernel: EFI: mem134: type=4, attr=0xf, range=[0x0000000075008000-0x0000000075009000) (0MB)

May 24 17:27:49 triton kernel: EFI: mem135: type=3, attr=0xf, range=[0x0000000075009000-0x000000007500c000) (0MB)

May 24 17:27:49 triton kernel: EFI: mem136: type=4, attr=0xf, range=[0x000000007500c000-0x000000007500e000) (0MB)

May 24 17:27:49 triton kernel: EFI: mem137: type=3, attr=0xf, range=[0x000000007500e000-0x000000007504a000) (0MB)

May 24 17:27:49 triton kernel: EFI: mem138: type=4, attr=0xf, range=[0x000000007504a000-0x00000000750f3000) (0MB)

May 24 17:27:49 triton kernel: EFI: mem139: type=3, attr=0xf, range=[0x00000000750f3000-0x0000000075168000) (0MB)

May 24 17:27:49 triton kernel: EFI: mem140: type=4, attr=0xf, range=[0x0000000075168000-0x000000007516e000) (0MB)

May 24 17:27:49 triton kernel: EFI: mem141: type=3, attr=0xf, range=[0x000000007516e000-0x0000000075198000) (0MB)

May 24 17:27:49 triton kernel: EFI: mem142: type=4, attr=0xf, range=[0x0000000075198000-0x00000000751d4000) (0MB)

May 24 17:27:49 triton kernel: EFI: mem143: type=3, attr=0xf, range=[0x00000000751d4000-0x00000000751df000) (0MB)

May 24 17:27:49 triton kernel: EFI: mem144: type=4, attr=0xf, range=[0x00000000751df000-0x00000000751fe000) (0MB)

May 24 17:27:49 triton kernel: EFI: mem145: type=3, attr=0xf, range=[0x00000000751fe000-0x0000000075205000) (0MB)

May 24 17:27:49 triton kernel: EFI: mem146: type=4, attr=0xf, range=[0x0000000075205000-0x0000000075279000) (0MB)

May 24 17:27:49 triton kernel: EFI: mem147: type=3, attr=0xf, range=[0x0000000075279000-0x000000007527d000) (0MB)

May 24 17:27:49 triton kernel: EFI: mem148: type=4, attr=0xf, range=[0x000000007527d000-0x000000007554d000) (2MB)

May 24 17:27:49 triton kernel: EFI: mem149: type=3, attr=0xf, range=[0x000000007554d000-0x0000000075550000) (0MB)

May 24 17:27:49 triton kernel: EFI: mem150: type=4, attr=0xf, range=[0x0000000075550000-0x0000000075588000) (0MB)

May 24 17:27:49 triton kernel: EFI: mem151: type=3, attr=0xf, range=[0x0000000075588000-0x000000007558b000) (0MB)

May 24 17:27:49 triton kernel: EFI: mem152: type=4, attr=0xf, range=[0x000000007558b000-0x00000000774a7000) (31MB)

May 24 17:27:49 triton kernel: EFI: mem153: type=6, attr=0x800000000000000f, range=[0x00000000774a7000-0x00000000774a9000) (0MB)

May 24 17:27:49 triton kernel: EFI: mem154: type=4, attr=0xf, range=[0x00000000774a9000-0x0000000077500000) (0MB)

May 24 17:27:49 triton kernel: EFI: mem155: type=10, attr=0xf, range=[0x0000000077500000-0x0000000077501000) (0MB)

May 24 17:27:49 triton kernel: EFI: mem156: type=6, attr=0x800000000000000f, range=[0x0000000077501000-0x000000007752b000) (0MB)

May 24 17:27:49 triton kernel: EFI: mem157: type=4, attr=0xf, range=[0x000000007752b000-0x000000007a604000) (48MB)

May 24 17:27:49 triton kernel: EFI: mem158: type=3, attr=0xf, range=[0x000000007a604000-0x000000007a605000) (0MB)

May 24 17:27:49 triton kernel: EFI: mem159: type=4, attr=0xf, range=[0x000000007a605000-0x000000007a614000) (0MB)

May 24 17:27:49 triton kernel: EFI: mem160: type=5, attr=0x800000000000000f, range=[0x000000007a614000-0x000000007a694000) (0MB)

May 24 17:27:49 triton kernel: EFI: mem161: type=6, attr=0x800000000000000f, range=[0x000000007a694000-0x000000007a6df000) (0MB)

May 24 17:27:49 triton kernel: EFI: mem162: type=0, attr=0xf, range=[0x000000007a6df000-0x000000007bf6a000) (24MB)

May 24 17:27:49 triton kernel: EFI: mem163: type=10, attr=0xf, range=[0x000000007bf6a000-0x000000007bf9a000) (0MB)

May 24 17:27:49 triton kernel: EFI: mem164: type=9, attr=0xf, range=[0x000000007bf9a000-0x000000007bfeb000) (0MB)

May 24 17:27:49 triton kernel: EFI: mem165: type=4, attr=0xf, range=[0x000000007bfeb000-0x000000007c000000) (0MB)

May 24 17:27:49 triton kernel: EFI: mem166: type=7, attr=0xf, range=[0x0000000100000000-0x0000000480000000) (14336MB)

May 24 17:27:49 triton kernel: EFI: mem167: type=11, attr=0x8000000000000001, range=[0x0000000080000000-0x0000000090000000) (256MB)

May 24 17:27:49 triton kernel: EFI: mem168: type=11, attr=0x8000000000000001, range=[0x00000000fe000000-0x00000000fe010000) (0MB)

Hello,

I intend to add a 2nd processor to this server. I am aware of the need to have the same processor and memory config.

The 5 parts I believe I need are:

processor, processor latch/heatsink, memory, air baffle for the memory, fan for the airbaffle,

Is there an options kit in the Australian HPE web store? What would it contain?

Is there someone who would post the correct part numbers (processor and memory excluded)

When I purchase these items, will I get access to the latest BIOS, as required byHP's best practice here.

Are there any parts I have missed?

Thanks in advance.

Simon

Please let me know if ML370 G5 supports HP LTO-6 6650 external SAS tape drive? if yes, is it possible through HP P600 Smart Array Controller?

We have a DL380p an MS60 with an 812 controller I need to just wipe 520 blockl if this doesnt work

what will. Desparate

Hi

I have HP Proliant DL380 G5 server with 8 Hardisk of 146GB. The controller is P400 and would like to start from scratch and setup as Raid 6. Will i be bale to do this.Not sure if i need to buy a licence for Raid 6. Also please post me a link to downlaod the HP Array configuration utility .

Thanks any help would be great

Hello all,

I was wondering if anybody had the chance to get the hands on installing Citrix XenServer 7 (Code named "Dundee"), released yesterday, on HPE ProLiant DL/ML Gen9 servers...especially when leaving them with UEFI boot enabled (actually, as reported here, XenServer 6.5 is tested to work only on some HPE ProLiant servers with BIOS in Legacy Mode since it doesn't support UEFI).

Any feedback from the field or is it really too early to ask?

Thanks!

PLEASE I NEED "IPMI" DRIVER AND "BASE  SYSTEM" FOR WINDOWS SERVER 2012

Buenos días tengo un HP Proliant Dl380 G9 al cual le instale Red hat Linux Enterprise despues de ello ha estado funcionando con normalidad 2 días al tercer día el sistema se colgo por largo rato lo cual me obligo a reiniciar de forma abrupta el sistema despues de esto al iniciar me sale el error "i8042.c can't read ctr while initializing i8042" y no arranca el sistema operativo. Ayuda por favor, gracias

The current box has 3 logical drives (the third one just added in) .shown in P410i Array Controller (F8 during POST) as:

• Logical Drive 1 - 2 SAS 72GB HD Raid10 <----OS disk
• Logical Drive 2 - 4 SAS 146GB HD Raid 5 <----data disk
• Logical Drive 3 - 2 SAS 146GB HD Raid10 <--- new OS disk

And this is what it shows in the OS :

bash-3.2# echo | format
Searching for disks...done

AVAILABLE DISK SELECTIONS:
       0. c0t0d0 <HP     -LOGICAL VOLUME -5.06 cyl 17841 alt 2 hd 255 sec 63>
          /pci@0,0/pci8086,3408@1/pci103c,3245@0/sd@0,0
       1. c0t1d0 <HP-LOGICAL VOLUME-5.70-410.10GB>
          /pci@0,0/pci8086,3408@1/pci103c,3245@0/sd@1,0
       3. c0t2d0 <HP -LOGICAL VOLUME -5.06 cyl 17841 alt 2 hd 255 sec 63>
          /pci@0,0/pci8086,3408@1/pci103c,3245@0/sd@2,0

The size of current rpool (c0t0d0) that contains the OS is too small which is 72GB. I want to increase the rpool by putting in new hard disks (2 SAS 146GB) and do the zpool attach the c0t2d0 to the rpool, after that I detach the c0t0d0. I make sure the new disk is bootable by setting

eeprom bootpath = /pci@0,0/pci8086,3408@1/pci103c,3245@0/sd@2,0

When i reboot the server and access the controller (F8), i also go to Select Boot Volume and select Logical Volume 3 as the new current boot lun. The server is able to boot up and picking up the new boot device correctly. However, I don't see 2 previous disks there anymore (c0t0d0 and c0t1d0).

bash-3.2# echo | format
Searching for disks...done


AVAILABLE DISK SELECTIONS:
       0. c0t2d0 <HP     -LOGICAL VOLUME -5.06 cyl 17841 alt 2 hd 255 sec 63>
          /pci@0,0/pci8086,3408@1/pci103c,3245@0/sd@2,0

I tried everything, devfsadm or cfgadm and reboot many times to check the status of those Logical Drives in the Controller, they are still there with OK status. But i don't know why i no longer see them in the OS. c0t0d0 is the old boot disk that i don't need anymore, but c0t1d0 is the data disk and i need it to show up here. Do you have any clues?

I have a DL360e Gen 8 and a DL360p Gen 8 each macine has (1) AJ672B  in each 1 is a back up

Installed the cards could not get any connectivity to the 6412 I did a loopback using HP 8gig SFPs.

Booted each server and the card was recognized my 6412has 2 modules in I plugeed into the second 

modle port 1 and changed the card bios in 1 card the common thing between the servers into the second moduke

port 1 againI only messed with the BIOS on the card in 1 server nothing on the second went to reboot both servers

in both servers the FC card was not recognied. How should I move forward

Hello,

i have 3 questions.
1 - my raid 5 array contains 5 harddisk with 300 GB. I want to add another harddisk (6 devices)
Do the array controller increase the capacity of the array WITHOUT loose the data?

2 - Same situation as 1. I change step by step all disks to 600 GB.
Old Array has 5 * 300. Does the controller increase to 5 * 600 WITHOUT loose the data? 

3- Same situation as 2.  When the controller doesnt increase the capacity, can I create a second Array?

Daniel

Hello,

I want mount an HP server ProLiant DL160 Gen6 to backup VMs and I want too attach to this server MSA60 and Google hasn't find answers for my questions ...

What is the compatibility of MSA60? Can I attach it to my ProLiant server? If yes, what's the hardware requirements ? 

Finaly, how much of SAS extension I can attach to my MSA60? For the limit capacity in SAS technology, I think that is 5.4 TB !

Thanks a lot ;-)

We have a DL980G7 server, there is no red or amber light on insight display but those server won't boot up, no beep sounds, no display appeared yet. When i look into inside chassis, there is an 00 code. Are there anybody could help me to solve this matter ? Thank's.

Hello,

First i did a RAID 1 and RAID5 with intelligent Provisionning. When starting the installation of Centos 5.8, the server does not detect the SAS disks in the array. I get the following message : "An error has occurred - no valid devices were found on which to create new file systems. Please check your hardware for the cause of this problem."

Thanks for your help.

I have a dead DL380 g6 with a p410i controller in it. I'm wondering if I can move the RAID 5 array (4disks and a hot spare) to a dl380 g9? The g9 has a P440ar controller in it. I know to keep the disk in the same order. Will that move work or is the p440ar to different to be able to read the meta from the disk to get them back up and running?

I have an issue that I've been beating to death for about 3 days now.  I have a brand new installation of vSphere 6.0.0, 3825889 using External Platform Service Appliance and seperate vCenter Server Appliances.  I've built a new W2K12 R2 VM and installed HPE OneView for vCenter.  The installation went flawlessley and I entered the correct FQDN of the vCenter appliance.  I viewed the certificate and it matches my FQDN name.  The result is the plugin shows in the Win32 client as disabled (expected) but NOTHING shows in the vSphere Web Client.  I have no web clients open anywhere during the installation.  I've rebooted both the PSC and VC appliances separately to no avail.  If I look at the MOB interface, there is an Extension entry for extensionList com.hp.ov4vc.ngc.all.v6.0 but there's no HPE Tab or Object anywhere to be found.  I'm at my wits end and I need resolution ASAP. 

I've removed and added the MOB entry multiple times, I can ping and NSLOOKUP the IP and FQDN of the VC and PSC and the OV4VC guest VM every which way.  I'm running Virtual Connect 4.5 and OneView 2.00.02-0219211.  I've completely deleted ALL VMs and appliancesa and rebuilt EVERYTHING from scratch and nothing is different. 

I do see the HP OneView for VMware vCenter (with the correct FQDN for vCenter) in the Administration --> Services list but when I right click on it, the options grey out immediately.  Lastly, I always attempt to register this product with vCenter using the Administrator@vsphere.local SSO account. 

Any ideas before I start recommending Dell products?  :P