Skip to main content

Partner Firmware Upgrade. PFU & Storage.

Friends, 

Today we are going to talk about PFU and Storage. 

Firmware upgrade on any device is always a risk as you are making changes on core software of that particular hardware and when you are doing on storage risk is always HIGH.

PFU: Partner Firmware upgrade.
You know started knowing about storage's ( Every Storage has 2 storage controller and 2 management controllers. Storage controller also referred as  SC and Management controllers are referred as MC.)

Every storage has redundancy maintain so when one controller goes down other one take cares but there are cases which i have seen entire storage went down. 

Normally people do Storage firmware upgrade when you have shutdown all your VM & Host  but you can do firmware upgrade when things up also using storage's redundancy feature.

Now if you wish to do Firmware upgrade of your storage while keeping everything is up what you have to do is 1st make sure your storage is health either by visual look at storage or web console or SSH connection. 

On SSH connection run command "Show Configuration" it will let you know status of all controllers.
Make sure MC is up ( so you can login and manage storage
Disable PFU  
One Storage controller at a time.

If you don't disable PFU what will happen is it try to sync both your controllers and reboot both controllers together which leads to " DISASTER" Your running VM's  non available, Data corruption etc.

Once you do PFU disable- To SSH connection or FTP connection to either A or B Management controller, Log-in with ID and Password. 
Next is you have to actually upgrade firmware hence type "PUT" space drop your firmware file on command prompt and then they command "Flash"

For example: Put D:\Firmware\TS****.bin Flash. Now let firmware get updated or upgraded in this entire process lot of programming will happen on both MC and SC controller and reboot both MC and SC and at last MC will be reboot
Add caption

Lets wait to get MC controller come back and everything is normal and firmware update is good than only attempt Firmware on Controller B. 
If some reason your firmware upgraded MC dont come back than take SSH or telnet from controller B and run command Restart MC A. (I am considering we are upgrading A controller 1st) you have to run this command 4-5 times and then your controller B will be Up. 

I hope you understand why you should disable PFU while attempting firmware. 










Comments

Popular posts from this blog

"kerberos: the specified credentials were rejected by the server", "unreachable": true" Ansible

Hello Friends, I was getting following Error while deploying my Ansible script, Basically my credential were getting rejected by server. SSH password: PLAY [Playbook_Name] ***************************************************************02:00:30 TASK [Gathering Facts] *********************************************************02:00:30 fatal: [Server_Inventory_Name]: UNREACHABLE! => {"changed": false, "msg": "kerberos: the specified credentials were rejected by the server", "unreachable": true} PLAY RECAP *********************************************************************02:00:30 Server_Inventory_Name    : ok=0    changed=0    unreachable=1   failed=0  It was resolved using one additional parameter in Inventory  i.e  "ansible_winrm_server_cert_vaildation:ignore"

NBSUTIL commands

Frustrated with syntax finding hence decided to post all NBSTLUTIL related commands so people will not face same problem. Common SLP Related Commands Show EMM Image list of Images that were backed up to an SLP STU [ -I / -U ] nbstlutil list nbstlutil list –lifecycle <name> nbstlutil list –backupid <id_value> nbstlutil list -image_state <value> nbstlutil list -copy_state <value> nbstlutil list -frag_state <value> nbstlutil list –mediaid <media_id>_–state 3 Activate /Inactivate SLP operations nbstlutil inactive –lifecycle <lifecycle name> nbstlutil inactive –backupid <backupid> nbstlutil active –lifecycle <lifecycle name> nbstlutil active –backupid <backupid> Cancel pending operations on selected image nbstlutil cancel -backupid <backupid> nbstlutil cancel -lifecycle <lifecycle> Show status on Incomplete copies of Lifecycle Managed images nbstlutil stlilist –lifecycle <lifecycle name> nbstlutil stlil

OSD or Onscreen menu is locked.

OSD or Onscreen menu is locked. I am having HP 20 Inch monitors on my Desk and was not able to change brightness and Sleep Timer etc for my monitor and was not able to get into the menu due to On Screen menu locked error. I know it's irritating issue. fix what i found for this is "Just hold menu button for 30 Sec and it will be solved. :)