HPE Storage Users Group

A Storage Administrator Community

Board index » Members Area » 3PAR Discussion



Post new topic Reply to topic  Page 1 of 1
  [ 3 posts ] 
  Print view Previous topic | Next topic 
Author Message
profp62
 Post subject: Upgradecage impact
PostPosted: Mon Mar 10, 2014 8:53 am 

Joined: Wed Feb 19, 2014 12:53 pm
Posts: 46
Hello all

Maybe it is a trivial (maybe stupid) question, but what is real impact of upgradecage on connected hosts ?

7200 connected to 3 node esxi cluster per two fabrics, correct multipathing - it is possible to do upgradecage online or not ?
I found only

"When the upgradecage command is issued, the drive cage becomes temporarily unavailable.
The cage automatically restarts following the firmware update, and may briefly disrupt the
loops during the restart. It is recommended showcage be used approximately one minute
after the update completes to ensure both loops to the cage are available again."

but its not clear enough for me.

Thanks
Top
 Profile  
Reply with quote  
Richard Siemers
 Post subject: Re: Upgradecage impact
PostPosted: Mon Mar 10, 2014 11:51 am 
Site Admin
User avatar

Joined: Tue Aug 18, 2009 10:35 pm
Posts: 1328
Location: Dallas, Texas
This year we updated two separate T800 units from 2.31 to 3.11, both upgrades included cage firmware updates, all online and non-disruptive. We had drive fail in Cage8 during the procedure which interupted the process and was manually restarted. Here is the output from the putty session:


Code:
ESFWT800-2 cli% showcage

Id Name   LoopA Pos.A LoopB Pos.B Drives Temp  RevA RevB Model Side
 0 cage0  4:0:1     0 5:0:1     0     40 24-34 2.61 2.61 DC4   n/a
 1 cage1  4:0:2     0 5:0:2     0     40 24-36 2.61 2.61 DC4   n/a
 2 cage2  4:0:3     0 5:0:3     0     40 24-34 2.61 2.61 DC4   n/a
 3 cage3  4:2:1     0 5:2:1     0     40 24-35 2.61 2.61 DC4   n/a
 4 cage4  4:2:2     0 5:2:2     0     40 24-32 2.61 2.61 DC4   n/a
 5 cage5  4:2:3     0 5:2:3     0     40 24-35 2.61 2.61 DC4   n/a
 6 cage6  6:0:1     0 7:0:1     0     40 26-36 2.61 2.61 DC4   n/a
 7 cage7  6:0:2     0 7:0:2     0     40 24-34 2.61 2.61 DC4   n/a
 8 cage8  6:0:3     0 7:0:3     0     40 25-35 2.61 2.61 DC4   n/a
 9 cage9  6:2:1     0 7:2:1     0     40 23-33 2.61 2.61 DC4   n/a
10 cage10 6:2:2     0 7:2:2     0     40 24-33 2.61 2.61 DC4   n/a
11 cage11 6:2:3     0 7:2:3     0     40 25-35 2.61 2.61 DC4   n/a
12 cage12 4:0:4     0 5:0:4     0     36 13-33 2.61 2.61 DC4   n/a
13 cage13 6:0:4     0 7:0:4     0     36 13-33 2.61 2.61 DC4   n/a
14 cage14 6:2:4     0 7:2:4     0     12 14-35 2.61 2.61 DC4   n/a
15 cage15 4:2:4     0 5:2:4     0     12 13-35 2.61 2.61 DC4   n/a
ESFWT800-2 cli%

ESFWT800-2 cli%

ESFWT800-2 cli% startupgradecage -a

Upgrading cage cage0 cpuA from rev 2.61 to revision in file /opt/tpd/fw/cage/dc4/lbod_fw.bin-2.64.
Beginning test after upgrade for cage0
cage0 passed test after upgrade
Upgrading cage cage1 cpuA from rev 2.61 to revision in file /opt/tpd/fw/cage/dc4/lbod_fw.bin-2.64.
Beginning test after upgrade for cage1
cage1 passed test after upgrade
Upgrading cage cage2 cpuA from rev 2.61 to revision in file /opt/tpd/fw/cage/dc4/lbod_fw.bin-2.64.
Beginning test after upgrade for cage2
cage2 passed test after upgrade
Upgrading cage cage3 cpuA from rev 2.61 to revision in file /opt/tpd/fw/cage/dc4/lbod_fw.bin-2.64.
Beginning test after upgrade for cage3
cage3 passed test after upgrade
Upgrading cage cage4 cpuA from rev 2.61 to revision in file /opt/tpd/fw/cage/dc4/lbod_fw.bin-2.64.
Beginning test after upgrade for cage4
cage4 passed test after upgrade
Upgrading cage cage5 cpuA from rev 2.61 to revision in file /opt/tpd/fw/cage/dc4/lbod_fw.bin-2.64.
Beginning test after upgrade for cage5
cage5 passed test after upgrade
Upgrading cage cage6 cpuA from rev 2.61 to revision in file /opt/tpd/fw/cage/dc4/lbod_fw.bin-2.64.
Beginning test after upgrade for cage6
cage6 passed test after upgrade
Upgrading cage cage7 cpuA from rev 2.61 to revision in file /opt/tpd/fw/cage/dc4/lbod_fw.bin-2.64.
Beginning test after upgrade for cage7
cage7 passed test after upgrade
Upgrading cage cage8 cpuA from rev 2.61 to revision in file /opt/tpd/fw/cage/dc4/lbod_fw.bin-2.64.
Beginning test after upgrade for cage8
Errors were present in test after upgrade
ESFWT800-2 cli% showcage

Id Name   LoopA Pos.A LoopB Pos.B Drives Temp  RevA RevB Model Side
 0 cage0  4:0:1     0 5:0:1     0     40 24-33 2.64 2.64 DC4   n/a
 1 cage1  4:0:2     0 5:0:2     0     40 24-35 2.64 2.64 DC4   n/a
 2 cage2  4:0:3     0 5:0:3     0     40 24-33 2.64 2.64 DC4   n/a
 3 cage3  4:2:1     0 5:2:1     0     40 24-34 2.64 2.64 DC4   n/a
 4 cage4  4:2:2     0 5:2:2     0     40 24-32 2.64 2.64 DC4   n/a
 5 cage5  4:2:3     0 5:2:3     0     40 24-34 2.64 2.64 DC4   n/a
 6 cage6  6:0:1     0 7:0:1     0     40 26-36 2.64 2.64 DC4   n/a
 7 cage7  6:0:2     0 7:0:2     0     40 24-34 2.64 2.64 DC4   n/a
 8 cage8  6:0:3     0 7:0:3     0     40 24-35 2.64 2.64 DC4   n/a
 9 cage9  6:2:1     0 7:2:1     0     40 23-33 2.61 2.61 DC4   n/a
10 cage10 6:2:2     0 7:2:2     0     40 24-33 2.61 2.61 DC4   n/a
11 cage11 6:2:3     0 7:2:3     0     40 25-35 2.61 2.61 DC4   n/a
12 cage12 4:0:4     0 5:0:4     0     36 13-33 2.61 2.61 DC4   n/a
13 cage13 6:0:4     0 7:0:4     0     36 13-33 2.61 2.61 DC4   n/a
14 cage14 6:2:4     0 7:2:4     0     12 13-35 2.61 2.61 DC4   n/a
15 cage15 4:2:4     0 5:2:4     0     12 13-35 2.61 2.61 DC4   n/a
ESFWT800-2 cli% upgradecage cage8

Skipping cage cage8 cpuA already up to date at rev 2.64
ESFWT800-2 cli% upgradecage -a

Skipping cage cage0 cpuA already up to date at rev 2.64
Skipping cage cage1 cpuA already up to date at rev 2.64
Skipping cage cage2 cpuA already up to date at rev 2.64
Skipping cage cage3 cpuA already up to date at rev 2.64
Skipping cage cage4 cpuA already up to date at rev 2.64
Skipping cage cage5 cpuA already up to date at rev 2.64
Skipping cage cage6 cpuA already up to date at rev 2.64
Skipping cage cage7 cpuA already up to date at rev 2.64
Skipping cage cage8 cpuA already up to date at rev 2.64
Upgrading cage cage9 cpuA from rev 2.61 to revision in file /opt/tpd/fw/cage/dc4/lbod_fw.bin-2.64.
Beginning test after upgrade for cage9
cage9 passed test after upgrade
Upgrading cage cage10 cpuA from rev 2.61 to revision in file /opt/tpd/fw/cage/dc4/lbod_fw.bin-2.64.
Beginning test after upgrade for cage10
cage10 passed test after upgrade
Upgrading cage cage11 cpuA from rev 2.61 to revision in file /opt/tpd/fw/cage/dc4/lbod_fw.bin-2.64.
Beginning test after upgrade for cage11
cage11 passed test after upgrade
Upgrading cage cage12 cpuA from rev 2.61 to revision in file /opt/tpd/fw/cage/dc4/lbod_fw.bin-2.64.
Beginning test after upgrade for cage12
cage12 passed test after upgrade
Upgrading cage cage13 cpuA from rev 2.61 to revision in file /opt/tpd/fw/cage/dc4/lbod_fw.bin-2.64.
Beginning test after upgrade for cage13
cage13 passed test after upgrade
Upgrading cage cage14 cpuA from rev 2.61 to revision in file /opt/tpd/fw/cage/dc4/lbod_fw.bin-2.64.
Beginning test after upgrade for cage14
cage14 passed test after upgrade
Upgrading cage cage15 cpuA from rev 2.61 to revision in file /opt/tpd/fw/cage/dc4/lbod_fw.bin-2.64.
Beginning test after upgrade for cage15
cage15 passed test after upgrade
ESFWT800-2 cli%

ESFWT800-2 cli%

ESFWT800-2 cli% showcage

Id Name   LoopA Pos.A LoopB Pos.B Drives Temp  RevA RevB Model Side
 0 cage0  4:0:1     0 5:0:1     0     40 24-33 2.64 2.64 DC4   n/a
 1 cage1  4:0:2     0 5:0:2     0     40 24-35 2.64 2.64 DC4   n/a
 2 cage2  4:0:3     0 5:0:3     0     40 24-33 2.64 2.64 DC4   n/a
 3 cage3  4:2:1     0 5:2:1     0     40 24-34 2.64 2.64 DC4   n/a
 4 cage4  4:2:2     0 5:2:2     0     40 24-32 2.64 2.64 DC4   n/a
 5 cage5  4:2:3     0 5:2:3     0     40 24-34 2.64 2.64 DC4   n/a
 6 cage6  6:0:1     0 7:0:1     0     40 26-36 2.64 2.64 DC4   n/a
 7 cage7  6:0:2     0 7:0:2     0     40 24-34 2.64 2.64 DC4   n/a
 8 cage8  6:0:3     0 7:0:3     0     40 25-35 2.64 2.64 DC4   n/a
 9 cage9  6:2:1     0 7:2:1     0     40 23-33 2.64 2.64 DC4   n/a
10 cage10 6:2:2     0 7:2:2     0     40 24-33 2.64 2.64 DC4   n/a
11 cage11 6:2:3     0 7:2:3     0     40 25-35 2.64 2.64 DC4   n/a
12 cage12 4:0:4     0 5:0:4     0     36 13-33 2.64 2.64 DC4   n/a
13 cage13 6:0:4     0 7:0:4     0     36 13-33 2.64 2.64 DC4   n/a
14 cage14 6:2:4     0 7:2:4     0     12 13-35 2.64 2.64 DC4   n/a
15 cage15 4:2:4     0 5:2:4     0     12 13-35 2.64 2.64 DC4   n/a

_________________
Richard Siemers
The views and opinions expressed are my own and do not necessarily reflect those of my employer.
Top
 Profile  
Reply with quote  
eve
 Post subject: Re: Upgradecage impact
PostPosted: Tue Mar 11, 2014 5:52 am 

Joined: Tue Oct 30, 2012 10:05 am
Posts: 26
You are correct that upgradecage will have some impact, but not for your hosts.
Hosts are not connected to a cage, but are connected to your InServ controllers.

What upgradecage will do is push the new firmware onto the FCAL modules in a cage,
and reboot the two FCAL's one by one to start the new firmware.
While rebooting you miss one path to your cage.
Top
 Profile  
Reply with quote  
Display posts from previous:  Sort by  
Post new topic Reply to topic  Page 1 of 1
  [ 3 posts ] 

Board index » Members Area » 3PAR Discussion

Who is online

Users browsing this forum: No registered users and 332 guests

You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Search for:
Jump to:  
cron
Powered by phpBB © 2000, 2002, 2005, 2007 phpBB Group | DVGFX2 by: Matt