shelf.module.configuration.failure:error

[#1]

Hi All

IHAC who has upgraded Data Ontap from 7.3.1 to 7.3.2 on a cluster.

During the process there were Shelf Module errors.

Customer wants to know what are these errors related to. Can anyone comment on these errors?

[shelf.module.configuration.failure:error]: ERROR--Could not complete the configuration of disk shelf module A on channels PARTNER/2c disk shelf ID 1.

[shelf.module.configuration.failure:error]: ERROR--Could not complete the configuration of disk shelf module A on channels PARTNER/2c disk shelf ID 4.

[shelf.module.configuration.failure:error]: ERROR--Could not complete the configuration of disk shelf module A on channels PARTNER/1b disk shelf ID 1.

[shelf.module.configuration.failure:error]: ERROR--Could not complete the configuration of disk shelf module A on channels PARTNER/2c disk shelf ID 5.

[shelf.module.configuration.failure:error]: ERROR--Could not complete the configuration of disk shelf module A on channels PARTNER/1b disk shelf ID 5.

[shelf.module.configuration.failure:error]: ERROR--Could not complete the configuration of disk shelf module A on channels PARTNER/2c disk shelf ID 3.

[shelf.module.configuration.failure:error]: ERROR--Could not complete the configuration of disk shelf module A on channels PARTNER/1b disk shelf ID 6.

[shelf.module.configuration.failure:error]: ERROR--Could not complete the configuration of disk shelf module A on channels PARTNER/1b disk shelf ID 4.

[shelf.module.configuration.failure:error]: ERROR--Could not complete the configuration of disk shelf module A on channels PARTNER/1b disk shelf ID 2.

Any comment will be really appreciated

[#2]

I just performed a cf takeover, and on the console of the partner (non active), I see the following:

Thu Apr 14 01:56:23 GMT [shelf.module.configuration.failure:error]: ERROR--Could not complete the configuration of disk shelf module A on channels 2a/2d disk shelf ID 1.

Waiting for giveback...(Press Ctrl-C to abort wait)Thu Apr 14 01:57:03 GMT [shelf.module.configuration.failure:error]: ERROR--Could not complete the configuration of disk shelf module B on channels 1b/0b disk shelf ID 1.

Thu Apr 14 01:57:03 GMT [shelf.module.configuration.failure:error]: ERROR--Could not complete the configuration of disk shelf module B on channels 1b/0b disk shelf ID 2.

Thu Apr 14 01:57:03 GMT [shelf.module.configuration.failure:error]: ERROR--Could not complete the configuration of disk shelf module B on channels 1b/0b disk shelf ID 3.

Thu Apr 14 01:57:04 GMT [shelf.module.configuration.failure:error]: ERROR--Could not complete the configuration of disk shelf module B on channels 1b/0b disk shelf ID 4.

Thu Apr 14 01:57:04 GMT [shelf.module.configuration.failure:error]: ERROR--Could not complete the configuration of disk shelf module B on channels 2a/2d disk shelf ID 2.

Anyone know what this means?

[#3]

Can you verify that there are no fault lights on any of the shelf modules?  If there are you can try reseating the module.  Otherwise you may need to call into support to have the module replaced.  It basically means it can't perform the module firmware update after the ONTAP upgrade since the shelf has no other working module to fall back on.

[#4]

Is there a way of checking for fault lights remotely?

I am not near the gear.  From Filer View, I see the happy green ball that says "The system's global status is normal."

[#5]

Hi,

    I would need the serial number to access any autosupports your filer may have sent up to trouble shoot the shelf modules.

Thanks,

Doug

[#6]

Never noticed before, but you may be right about the shelf not upgrading:

               Shelf 1: ESH4  Firmware rev. ESH A: 13  ESH B: 13

                Shelf 2: ESH4  Firmware rev. ESH A: 13  ESH B: 13

                Shelf 3: ESH4  Firmware rev. ESH A: 13  ESH B: 13

                Shelf 4: ESH4  Firmware rev. ESH A: 13  ESH B: 13

               Shelf 1: ESH4  Firmware rev. ESH A: 13  ESH B: 13

                Shelf 2: ESH4  Firmware rev. ESH A: 13  ESH B: 13

                Shelf 3: ESH4  Firmware rev. ESH A: 14  ESH B: 14

                Shelf 4: ESH4  Firmware rev. ESH A: 14  ESH B: 14

So at least some shelves are at 14.

I did a disk_fw_update:

Wed Apr 13 19:36:24 PDT [na2: dfu.firmwareUpToDate:info]: Firmware is up-to-date on all disk drives

Just downloaded ESH4.1400.SFW into /etc/shelf_fw, going to see if shelf upgrade is needed.

Filer na2.vm.local   Model FAS3040   System ID 0118061032   Version 7.3.3   Volumes 26 Volumes   Aggregates 2 Aggregates   Disks 70 Disks
(5 spare, 0 failed)   Status The system's global status is normal.

[#7]

What is the output of the following command:

storage download shelf

[#8]

storage shelf download

Actually I was behind, I updated it:

Wed Apr 13 19:58:45 PDT [na2: sfu.ctrllerElmntsPerShelf:info]: [storage download shelf]: 2 ES controller elements can be updated on 0d.shelf1.

Wed Apr 13 19:58:45 PDT [na2: sfu.ctrllerElmntsPerShelf:info]: [storage download shelf]: 2 ES controller elements can be updated on 0d.shelf2.

Wed Apr 13 19:58:45 PDT [na2: sfu.ctrllerElmntsPerShelf:info]: [storage download shelf]: 2 ES controller elements can be updated on 0b.shelf1.

Wed Apr 13 19:58:45 PDT [na2: sfu.ctrllerElmntsPerShelf:info]: [storage download shelf]: 2 ES controller elements can be updated on 0b.shelf2.

Wed Apr 13 19:58:45 PDT [na2: sfu.ctrllerElmntsPerShelf:info]: [storage download shelf]: 2 ES controller elements can be updated on 0b.shelf3.

Wed Apr 13 19:58:45 PDT [na2: sfu.ctrllerElmntsPerShelf:info]: [storage download shelf]: 2 ES controller elements can be updated on 0b.shelf4.

Wed Apr 13 19:58:45 PDT [na2: sfu.downloadStarted:info]: Update of disk shelf firmware started on 6 shelves.

Wed Apr 13 19:58:45 PDT [na2: sfu.downloadingController:info]: [storage download shelf]: Downloading ESH4.1400.SFW on disk shelf controller module A on 0b.shelf3.

Wed Apr 13 19:58:45 PDT [na2: sfu.downloadingController:info]: [storage download shelf]: Downloading ESH4.1400.SFW on disk shelf controller module A on 0b.shelf4.

Wed Apr 13 19:58:45 PDT [na2: sfu.downloadingController:info]: [storage download shelf]: Downloading ESH4.1400.SFW on disk shelf controller module A on 0b.shelf2.

Wed Apr 13 19:58:45 PDT [na2: sfu.downloadingController:info]: [storage download shelf]: Downloading ESH4.1400.SFW on disk shelf controller module A on 0b.shelf1.

Wed Apr 13 19:58:45 PDT [na2: sfu.downloadingController:info]: [storage download shelf]: Downloading ESH4.1400.SFW on disk shelf controller module A on 0d.shelf1.

Wed Apr 13 19:58:45 PDT [na2: sfu.downloadingController:info]: [storage download shelf]: Downloading ESH4.1400.SFW on disk shelf controller module A on 0d.shelf2.

Wed Apr 13 19:58:45 PDT [na2: sfu.downloadingController:info]: [storage download shelf]: Downloading ESH4.1400.SFW on disk shelf controller module A on 0b.shelf4.

Wed Apr 13 19:58:45 PDT [na2: sfu.downloadingController:info]: [storage download shelf]: Downloading ESH4.1400.SFW on disk shelf controller module A on 0b.shelf1.

Wed Apr 13 19:58:45 PDT [na2: sfu.downloadingController:info]: [storage download shelf]: Downloading ESH4.1400.SFW on disk shelf controller module A on 0b.shelf3.

Wed Apr 13 19:58:45 PDT [na2: sfu.downloadingController:info]: [storage download shelf]: Downloading ESH4.1400.SFW on disk shelf controller module A on 0b.shelf2.

Wed Apr 13 20:00:00 PDT [na2: kern.uptime.filer:info]:   8:00pm up  1:04 2348142 NFS ops, 103601 CIFS ops, 23 HTTP ops, 1079982 FCP ops, 3206 iSCSI ops

Wed Apr 13 20:00:00 PDT [na2: kern.timed.adjust:info]: server '0.pool.ntp.org' reports the appliance date is fast by 0.446 seconds. Adjusting date.

Wed Apr 13 20:02:12 PDT [na2: sfu.downloadingController:info]: [storage download shelf]: Downloading ESH4.1400.SFW on disk shelf controller module B on 0d.shelf2.

Wed Apr 13 20:02:12 PDT [na2: sfu.downloadingController:info]: [storage download shelf]: Downloading ESH4.1400.SFW on disk shelf controller module B on 0d.shelf1.

Wed Apr 13 20:02:31 PDT [na2: sfu.downloadingController:info]: [storage download shelf]: Downloading ESH4.1400.SFW on disk shelf controller module B on 0b.shelf3.

Wed Apr 13 20:02:34 PDT [na2: sfu.downloadingController:info]: [storage download shelf]: Downloading ESH4.1400.SFW on disk shelf controller module B on 0b.shelf2.

Wed Apr 13 20:02:34 PDT [na2: sfu.downloadingController:info]: [storage download shelf]: Downloading ESH4.1400.SFW on disk shelf controller module B on 0b.shelf1.

Wed Apr 13 20:02:34 PDT [na2: sfu.downloadingController:info]: [storage download shelf]: Downloading ESH4.1400.SFW on disk shelf controller module B on 0b.shelf4.

Wed Apr 13 20:05:40 PDT [na2: sfu.downloadSuccess:info]: [storage download shelf]: Firmware file ESH4.1400.SFW downloaded on 0d.shelf2.

Wed Apr 13 20:05:40 PDT [na2: sfu.downloadSuccess:info]: [storage download shelf]: Firmware file ESH4.1400.SFW downloaded on 0d.shelf1.

Wed Apr 13 20:05:57 PDT [na2: ems.engine.inputSuppress:warning]: Event 'openssh.invalid.channel.req' suppressed 2 times since Wed Apr 13 20:00:46 PDT 2011.

Wed Apr 13 20:05:57 PDT [na2: openssh.invalid.channel.req:warning]: SSH client (SSH-2.0-OpenSSH_4.3) from 10.1.12.30 sent unsupported channel request (10, env).

Wed Apr 13 20:06:19 PDT [na2: sfu.downloadSuccess:info]: [storage download shelf]: Firmware file ESH4.1400.SFW downloaded on 0b.shelf3.

Wed Apr 13 20:06:22 PDT [na2: sfu.downloadSuccess:info]: [storage download shelf]: Firmware file ESH4.1400.SFW downloaded on 0b.shelf1.

Wed Apr 13 20:06:22 PDT [na2: sfu.downloadSuccess:info]: [storage download shelf]: Firmware file ESH4.1400.SFW downloaded on 0b.shelf2.

Wed Apr 13 20:06:22 PDT [na2: sfu.downloadSuccess:info]: [storage download shelf]: Firmware file ESH4.1400.SFW downloaded on 0b.shelf4.

Wed Apr 13 20:06:22 PDT [na2: sfu.downloadSummary:info]: Shelf firmware updated on 6 shelves.

na2*> storage download shelf

[storage download shelf]: No shelves eligible for update

I guess I could try to do a cf failover again and see if it tosses those errors.

[#9]

Please do, let me know if you need anything else I'll be online for 30 more minutes.