3par 8200 - 2 nodes 2 enclosures. It was working fine for a long time. I'm attempting to add a third enclosure. The enclosure is an M6710 that was previously connected to a 3par 7200 system. The I/0 cards on the M6710 have been replaced with cards from an 8000 series enclosure sourced from ebay.
The system seems to recognize it, but it needs a firmware update. When attempting to update it there are errors.
For one thing, the system sees the cards in the new cage in opposite positions. I was very careful to follow the cabling guides and have checked several times. The card that is in the top, the system sees as card 0 instead of 1. When trying to upgrade previously, it wanted the cabling swapped between the cards: ==================================================== cage3 - Move (cage3, I/O 0, DP-1) to (cage3, I/O 1, DP-1) cage3 - Move (cage3, I/O 0, DP-2) to (cage3, I/O 1, DP-2) cage3 - Move (cage3, I/O 1, DP-1) to (cage3, I/O 0, DP-1) ==================================================== But after adjusting the cabling as prescribed, checkhealth returns an error about the Loops being on the wrong nodes : ==================================================== Cage cage:3 LoopA should be on even node Cage cage:3 LoopB should be on odd node Cage cage:3 Firmware is not current =====================================================
I'm wondering if it's trying to upgrade something other than the cards. We tried to swap the card with a known good one in a different enclosure to see if we could make it upgrade there. But once we do that, the system reports everything the same - firmware update needed on the same cage. It doesn't see anything needing an upgrade in the known good enclosure with the suspect card from the M6710, but it sees the same errors on the M6710 with that known good card there.
At this point I'm not sure what else to try except removing the enclosure, switching places for card 0 and 1, and attempting again, but I don't think that's the problem.
I can't find any reference to this 'enclmgmt failed parsing upgrade request' anywhere. I'm wondering if I'm trying to do something that's not supposed to work?
Thanks in advance for any insight.
------------------------------------------------------------------------- ==================================================== % showversion -a -b Release version 3.3.2.135 Patches: P01
Component Name Version CLI Server 3.3.2.140 (P01) CLI Client 3.3.2.140 System Manager 3.3.2.140 (P01) Kernel 3.3.2.135 TPD Kernel Code 3.3.2.135 TPD Kernel Patch 3.3.2.140 (P01) CIM Server 3.3.2.140 (P01) WSAPI Server 3.3.2.135 Console Menu 3.3.2.135 Event Manager 3.3.2.135 Internal Test Tools 3.3.2.135 LD Check Tools 3.3.2.135 Network Controller 3.3.2.140 (P01) Node Disk Scrubber 3.3.2.135 PD Scrubber 3.3.2.135 Per-Node Server 3.3.2.135 Persistent Repository 3.3.2.135 Powerfail Tools 3.3.2.135 Preserved Data Tools 3.3.2.140 (P01) Process Monitor 3.3.2.135 Software Updater 3.3.2.135 TOC Server 3.3.2.135 VV Check Tools 3.3.2.140 (P01) Upgrade Tool 210713.U038 File Persona 1.6.101.1-20201118 SNMP Agent 1.14.0 SSH 7.9p1-10 VASA Provider 3.1.9.3 (P01) Legacy FW Database 3.3.2.135 Legacy Drive FW 3.3.2.135 Emulex Drive FW 3.3.2.135 Legacy HGST Drive FW 3.3.2.135 Samsung FIPS Drive FW 3.3.2.135 Samsung nonFIPS FW 3.3.2.135 Seagate FIPS Drive FW 3.3.2.135 Seagate nonFIPS FW 3.3.2.135 WDC FIPS 10K Drive FW 3.3.2.135 WDC FIPS 15K Drive FW 3.3.2.135 WDC FIPS SSD FW 3.3.2.135 WDC nonFIPS 10K FW 3.3.2.135 WDC nonFIPS 15K FW 3.3.2.135 WDC nonFIPS 7.2K FW 3.3.2.135 WDC nonFIPS SSD FW 3.3.2.135 Intel SCM FW 3.3.2.135 UEFI BIOS 05.05.07 MCU Firmware (OKI) 4.9.20 MCU Firmware (STM) 5.5.00 Cage Firmware (DC1) 4.44 Cage Firmware (DC2) 2.64 Cage Firmware (DC3) 08 Cage Firmware (DC4) 2.64 Cage Firmware (DCN1) 409b Cage Firmware (DCN2) 409b Cage Firmware (DCS1) 409b Cage Firmware (DCS2) 409b Cage Firmware (DCS5) 3.07 Cage Firmware (DCS6) 3.07 Cage Firmware (DCS7) 409b Cage Firmware (DCS8) 409b QLogic QLA4052C HBA Firmware 03.00.01.77 QLogic QLE8242 CNA Firmware 04.15.27 QLogic 260x HBA FC Firmware 174.03.70 QLogic 27xx/268x HBA FC Firmware 174.03.70 QLogic 83xx HBA FCoE Firmware 08.01.05 QLogic 8300 HBA iSCSI Firmware 05.07.51 Emulex LP11002 HBA Firmware 02.82.x10 Emulex LPe12002 HBA Firmware 02.10.x08 Emulex LPe12004 HBA Firmware 02.10.x08 Emulex LPe16002 HBA Firmware 11.4.415.0 Emulex LPe16004 HBA Firmware 11.4.415.0 3PAR FC044X HBA Firmware 200A8 LSI 9201-16e HBA Firmware 20.00.13 LSI 9205-8e HBA Firmware 20.00.13 LSI 9300-8e HBA Firmware 10.10.03 ====================================================
==================================================== % admithw -checkonly Checking nodes... Checking volumes... Checking system LDs... After an upgrade from 2.2.4 or earlier, if sufficient space is present admithw will automatically remove and recreate the preserved data LDs with a larger set size to improve their availability Checking ports... Checking SAS HBA firmware... Checking 4 SAS Port(s) for firmware upgrades Checking state of disks... Checking for drive table upgrade packages Checking cabling... Checking cage firmware... 1 cage(s) require firmware upgrades. This will require approximately 15-60 minutes Checking system health... Checking alert Checking ao Checking cabling Checking cage Checking cert Checking dar Checking date Checking file Checking fs Checking host Checking hostkeys Checking ld Checking license Checking network Checking node Checking pd Checking pdch Checking port Checking qos Checking rc Checking snmp Checking task Checking vlun Checking vv Checking sp No issues reported. admithw has completed ====================================================
==================================================== % admithw -notune -ni Checking nodes... Checking volumes... Checking system LDs... Checking ports... Checking SAS HBA firmware... Checking 4 SAS Port(s) for firmware upgrades Checking state of disks... Checking cabling... Checking if this is an upgrade that added new drive types... Checking for disks to admit... Admitting PDs: this step can take an extended period of time based on load 0 disks admitted Checking admin volume... Admin volume exists Checking cage firmware... 1 cage(s) require firmware upgrades. This will require approximately 15-60 minutes 2023-11-27 09:23:50 EST Upgrading cage firmware in parallel Upgrading all cages in parallel. Please monitor the progress with "upgradecage -status". ERROR: unable to start upgrade: enclmgmt failed parsing upgrade request. ====================================================
==================================================== % upgradecage -status Cage OverallState StartTime StopTime Current State Pending Completed FailureDetail cage0 succeeded 2023-11-01 21:01:02 EDT 2023-11-01 21:03:51 EDT -- -- -- sepA -- cage1 skipped -- -- -- -- -- -- -- cage2 skipped -- -- -- -- -- -- -- ====================================================
-------------------------------------------------------------------------
|