This post is more than 5 years old

6 Posts

2630

August 27th, 2016 10:00

PS6500e Firmware 4.2 upgrade path and best practices

recently took over administration of a PS6500E 42 1TB drives, M1000 , PC6224 these units have sat unused for several years. ~5-8  I dont think it was ever used !  Time has been limited to undertake this task, however, I have downloaded and read though lots of documentation as time permits. .

Taking small steps to verify functionality of the hardware was my first priority. 

SIMPLE hardware overview:

> PE R710

> PS6500E

> PC6224

> M1000 w/ 16 blades

< START TESTING>

--> create an account on the Eql support site

--> created an account here!

--> Documented the original config wiring, network topology.

--> All firmware documented on all units ( dont have on hand as I write this aaarg!)

--> re-cabled , stripping everything out and restarting at a know topology. (KISS)

--> Rebuilt head-node R710 with RHEL-6.8.

--> Rebuilt all Blade Servers (16) with RHEL-6.8

--> created user accounts for testing on all systems

--> installed use required SW for development

--> Explained to the users this is the testing stage ONLY

--> Users started testing functionality, ( adding more requirements along the way ! )

--> Explained to the users this is the testing stage ONLY. LOL

--> Users testing functionality, ( adding more requirements, You get the picture im sure)

--> added 144G RAM to the head-node. ( 8G Originally )

--> Added 8TB USB drive for data storage ( user did this ..aarg! )

--> NFS share (8TB USB) from head-node to BS1-16 ( more requirements added )

--> Created test user account on the NFS share /users/home and accessible across all systems

At this point I need to get the PS6500E online ant tested before this monster grow out of control.

I was able to gain access to the unit via serial connection resetting the grpadmin password and running setup via command line. 

I now have access to the GUI and performed some testing to the point of creating and connecting to a new volume via iSCSI to the head node.  

--> Network config overview:

--> MGMT == 192.168.1.0/24 ( IPMI / Dell mgmt?) CMC

--> Compute == 192.168.2.0/24 network comm. head-node and the 16 blades

--> PS6500 / R710 iSCSI = = 10.0.50.0/24 network comm. head-node and PS6500E

--> PC6224 == Have not gained access to this unit, yet.  Seems like a flat configured swx

--> M1000 2 x SWX modules and 2 x CMC modules connected together and 1 cable to the PC6224

--> KVM interconnection works to all nodes ( never use it though )

What is the best path to get the firmware on all this stuff updated and at the current version.  I'm not worried about data loss at this point.  Remember we are TESTING!!!

Thanks for taking the time and I appreciate any help, advise, comments.

6 Posts

August 27th, 2016 17:00

Thank you for your support.

I do have access to eqlsupport.dell.com and have downloaded the following based on your recommendations :

V5-0-2.tar

kit_V5.2.11-R363455_2108498646.tgz

kit_V6.0.11-R393352_4057775981.tgz

V7-1-11-R422460.zip

V8-1-3-R422462.zip

V9-0-0-R424354.zip

Does this look correct?

I will work on the Switch upgrade next.

Thank you again for your time and knowledge

V/R

John

6 Posts

August 30th, 2016 05:00

Thanks for the guidance.

V5-0-2.tar

kit_V5.2.11-R363455_2108498646.tgz

kit_V6.0.11-R393352_4057775981.tgz

V7-1-11-R422460.zip

V8-1-3-R422462.zip

V9-0-0-R424354.zip

List and order of the firmware to be installed.

6 Posts

August 31st, 2016 05:00

We have support and the an account to get the firmware.


I was able to update the firmware in the steps above until v7 successfully.

V7 flashed ok, however, the GUI fails to run properly. Big fat ERROR when loading the web GUI.  The error log reveals a missing file

6 Posts

September 2nd, 2016 13:00

-->  was using https

-->  Java   v1.8.101-b13 .. 1.8.102 is the very latest though

--> I can ssh into the unit w/o any issues

--> Run as application fails too.... ERROR

I'm pushing forward in hopes that v8 will correct the issues I'm seeing now.

I was able to ftp v8 and start the update process via ssh

6 Posts

September 2nd, 2016 15:00

V8 update went well with the same java ERROR though. ERROR

Restarting after updating to v9 just now. (both controllers are now running v9)

OS RHEL 6.8 with the latest updates applied

After looking closer at the ERROR and my firefox extensions here is what I've found:

Firefox -- 45.3.0

IceTea-Web Plugin == 1.6.2 (rhel-1.el6-x86_64)

Group Manager requires java SE 6 update 30. For Some reason RHEL is not at this particular version just yet!

<-- Work around  -->

Downloaded the app: groupmgr.jnpl

untared my latest java 8.102 to a temp location /***/java

had to give the full path when running:

/***/java/version/bin/javaws /coolstuff/groupmgr.jnpl &

Just like that, it works.

Thanks for the assistance

No Events found!

Top