sa_taku's Posts

sa_taku's Posts

Hi sjones5, Thanks, I got it.
Hi sjones5, However I understood what you mean, I have additional question. Can I downgrade Node Firm Package 10.0.1 to 9.3.5?? I upgraded NFP to 10.0.1.  ;(
Hi alandelgado, Thanks for your reply. I got it.
Hi sjones5, Thanks for your reply. I understood what are Gen5 , Gen6 and the 40GB NICs. I have another question. If you don't mind, could you answer it? question: Our customer has ... See more...
Hi sjones5, Thanks for your reply. I understood what are Gen5 , Gen6 and the 40GB NICs. I have another question. If you don't mind, could you answer it? question: Our customer has Gen5 hardware (NL410). According to Release note, we must not apply Node Firmware Package 10.0.1 in this condition, correct?? Do we have to apply Node firmware Package 9.3.5?
https://support.emc.com/docu69984_Isilon-Node-Firmware-Package-10.0.1-Release-Notes.pdf Hi, I read the following document. [Isilon Node firmware Package version 10.0.1 Release Notes] In... See more...
https://support.emc.com/docu69984_Isilon-Node-Firmware-Package-10.0.1-Release-Notes.pdf Hi, I read the following document. [Isilon Node firmware Package version 10.0.1 Release Notes] In this document, EMC says the following warning on page2. <! CAUTION> Only update firmware with this package if your cluster contains Generation 6 hardware or Generation 5 with 40G Ethernet cards. If your cluster does not contain Generation 6 or Gen5 with 40GB Ethernet cards, update your firmware with  the 9.3.5 Node Firmware package. I'd like to know which hardwares are Gen6 or Gen5. How can I specify the Generation of the node?? And I'd like to know what is "40GB Ethernet cards" on Gen5. Is the 40GB Ethernet card different from IB card? If anyone know, please let me know.
Hi alandelgado, Thanks for your information how to resolve this issue. I have a question. How can I specify the node ID???
Hi sjones5, Our engineer collected isi_gather_info twice. It was before and after executing "#isi upgrade cluster firmware devices" command. <isi_gather_info which was collected before the... See more...
Hi sjones5, Our engineer collected isi_gather_info twice. It was before and after executing "#isi upgrade cluster firmware devices" command. <isi_gather_info which was collected before the command>     Device                                     Type                          Firmware                        Nodes -- ---------------------------------------------------------------------------------------------------------------------------     CFFPS1                                  CFFPS                       04.14                               5     CFFPS1                                  CFFPS                       02.02                               1-4     CFFPS2                                  CFFPS                       04.14                               5     CFFPS2                                  CFFPS                       02.02                               1-4 <executed command> #isi upgrade cluster firmware devices     Device                                     Type                           Firmware                          Nodes -- -----------------------------------------------------------------------------------------------------------------------------    CFFPS2_Optimus_Flex            CFFPS                        04.14                               1,5    CFFPS1_Optimus_Flex            CFFPS                        04.14                               1,5    CFFPS1_Optimus_Acbel          CFFPS                        02.02                               1-4    CFFPS2_Optimus_Acbel          CFFPS                        02.02                               1-4 <isi_gather_info which was corrected after the command>    Device                                      Type                           Firmware                           Nodes -- ------------------------------------------------------------------------------------------------------------------------------     CFFPS1                                  CFFPS                        04.14                                 5     CFFPS1                                  CFFPS                        02.02                                 1-4     CFFPS2                                  CFFPS                        04.14                                 5     CFFPS2                                  CFFPS                        02.02                                 1-4 I think the reference sources are different between isi_gather_info and "isi upgrade cluster firmware devices" command. Yesterday I opened SR to investigate this issue , but I haven't gotten any response yet.
Hi Phil Lam, I write the command output.(just only items which is related to this issue) #isi upgrade nodes firmware progress Lnns            Device                                    Old ... See more...
Hi Phil Lam, I write the command output.(just only items which is related to this issue) #isi upgrade nodes firmware progress Lnns            Device                                    Old Version                        New Version                              Status ---------------------------------------------------------------------------------------------------------------------------------------------------- 1                  CFFPS1_Optimus_Acbel        02.02                                 02.02                                          - 1                  CFFPS1_Optimus_Flex           04.14                                 04.14                                         - 1                  CFFPS2_Optimus_Acbel         02.02                                 02.02                                         - 1                  CFFPS2_Optimus_Flex           04.14                                 04.14                                         - 2                  CFFPS1_Optimus_Acbel         02.02                                 02.02                                         - 2                  CFFPS2_Optimus_Acbel         02.02                                 02.02                                         - ・・・ 5                  CFFPS1_Optimus_Flex             04.14                                 04.14                                         - 5                  CFFPS2_Optimus_Flex             04.14                                 04.14                                        -  //However I don't know why there are four items for Lnn1, I think the upgrade process has been finished correctly.    //Because the status collums are empty. (not "upgrading" or "queued") #isi upgrade cluster firmware devices Device                                    Type                                 Firmware                       Mismatch                   Lnns ------------------------------------------------------------------------------------------------------------------------------------- CFFPS2_Optimus_Flex         CFFPS                             04.14                             False                          1,5 CFFPS1_Optimus_Flex         CFFPS                             04.14                             False                          1,5 CFFPS1_Optimus_Acbel       CFFPS                             02.02                             False                          1-4 CFFPS2_Optimus_Acbel       CFFPS                             02.02                             False                           1-4 Unfortunately, our customer hasn't allow us to execute the command again.
Hi sjones5, Thanks for your response. I checked isi_gather_info, and found below. <node1\isi_hw_status> PwrSupl: PS1 (type=ACBEL POLYTECH, fw=02.02) PwrSupl: PS2 (type=ACBEL POLYTECH, fw... See more...
Hi sjones5, Thanks for your response. I checked isi_gather_info, and found below. <node1\isi_hw_status> PwrSupl: PS1 (type=ACBEL POLYTECH, fw=02.02) PwrSupl: PS2 (type=ACBEL POLYTECH, fw=02.02) Power Supplies OK Power Supply 1 good Power Supply 2 good <local\firmware> Device                                Type                      Firmware                    Nodes -------------------------------------------------------------------------------------------------------------- CFFPS1                             CFFPS                   04.14                         5 CFFPS1                             CFFPS                   02.02                         1-4 CFFPS2                             CFFPS                   04.14                         5 CFFPS2                             CFFPS                   02.02                         1-4 I understood that the  command that had been executed by our engineer was incorrect. (the output of isi_gather_info file is correct.) Do you know the the command is incorrect? Regards, Taku
Hi sjones5, Thanks you for your answer. Do you know why just only lnn1 appears on all of the CFFPS?? Is it related to replace power supplys?
Hi, Our customer has an Isilon cluster of NL410×5. Our engineer executed the following command.   #isi upgrade cluster firmware devices And the output is below. #isi upgrade cluster firm... See more...
Hi, Our customer has an Isilon cluster of NL410×5. Our engineer executed the following command.   #isi upgrade cluster firmware devices And the output is below. #isi upgrade cluster firmware devices Device          Type          Firmware               Mismatch     Lnns ----------------------------------------------------------------------------------- QLogic-NX2     10GigE     7.13.0                    -                    1-5 BMC_S1400FP BMC        1.25.9722              -                    1-5 CFFPS1            CFFPS     04.14                    -                     1,5    CFFPS1            CFFPS     02.02                    -                      1-4 CFFPS2            CFFPS     04.14                    -                       1,5 CFFPS2             CFFPS    02.02                    -                       1-4 ... I'd like to know why the LNN 1 appears on all  CFFPS collums. And to now what is the CFFPS. I think the CFFPS is Power Supply unit firmware, is it correct?? Regards,
Hi, Our customer has a cluster  which consists of  S210&X410, and he is planning to upgrade OneFS 8.0.0.3 to 8.0.0.4, because there are many firmware problems on OneFS 8.0.0.3. Before Upgra... See more...
Hi, Our customer has a cluster  which consists of  S210&X410, and he is planning to upgrade OneFS 8.0.0.3 to 8.0.0.4, because there are many firmware problems on OneFS 8.0.0.3. Before Upgrading OneFS, we are reading  "Upgrade Planning and Process Guide". In the document, the following description are written on P.37 "Preserve the Kerberos keytab file" Though our customer has been using the Kerberos authentification, we can't find the /etc/<name>.keytab file and /etc/mcp/override/user_preserve_files.xml file. In this stiuation,  do we have to do the procedure in "Preserve the Kerberos keytab file" section?? Regards,
Hi sjones5, Thanks for your response. I'm going to open a case. Regards, Taku
Hi, Our customer has a cluster  which consists of  S210&X410, and he upgraded OneFS 8.0.0.0 to 8.0.0.3. After upgrading, he noticed that the interited permission on all SMB directories had go... See more...
Hi, Our customer has a cluster  which consists of  S210&X410, and he upgraded OneFS 8.0.0.0 to 8.0.0.3. After upgrading, he noticed that the interited permission on all SMB directories had gone.(disabled) Does anyone have the same experience?? And how can I investigate this problem? Our customer are planning to upgrade OneFS 8.0.0.3 to 8.0.0.4, because there are many firmware problems on OneFS 8.0.0.3 . He is wondering the same problem will occur again after upgrading OneFS.
Thanks Jozi,  I got it.
Hi mattashton, I have two questions. Where did you find this information from? And do you know whether the Slow pulse blue LED isn't normal when the node is in the cluster?
Hi, My customer has had the same issue which Ryan_CSULB had. The cluster is S210 and X410, and OneFS version is 8.0.0.3. I opened SR, and was asked to do "/usr/bin/isi_hwtools/isi_fputil -g"... See more...
Hi, My customer has had the same issue which Ryan_CSULB had. The cluster is S210 and X410, and OneFS version is 8.0.0.3. I opened SR, and was asked to do "/usr/bin/isi_hwtools/isi_fputil -g" described in KB304494. But I think the KB is for S200,X200,X400 and NL400, correct? Does anyone know the command for S210,X210,X410 and NL410??
Hi, Our customer has a Isilon clustoer running in OneFS 8.0.0.3. And the size of isi_gather_info has been too big, almost 3GB. I'd like to know how to reduce the size of isi_gather_info. ... See more...
Hi, Our customer has a Isilon clustoer running in OneFS 8.0.0.3. And the size of isi_gather_info has been too big, almost 3GB. I'd like to know how to reduce the size of isi_gather_info. I found that the "minidump.tar" file in a node was 2.5GB. And I found a commnad option for isi_gather_info when Iread CLI administration document for OneFS 8.0.0. --clean-cores --clean-dumps --clean-all Which command delete the minidump file, and reduce the size of isi_gather_info???
Hi I updated Isilon OneFS 7.2.1.1 to 8.0.0.0 in May, 2016. When I had used OneFS7.2.1.1, I set up the notification by the Web. I could control when the nofitication occuered by the checkbox(... See more...
Hi I updated Isilon OneFS 7.2.1.1 to 8.0.0.0 in May, 2016. When I had used OneFS7.2.1.1, I set up the notification by the Web. I could control when the nofitication occuered by the checkbox(Information, Warning, Critical, Emergency) for individual events. But I cannot contorl when the notification occur because the checkbox vanish in OneFS8.0.0.0. Can I control when the notification occur in OneFS 8.0.0.0? If I can, would you tell me the way?
Hi I got the answer from EMC technical engineer. [answer] It's expected. Since as for mount process, NFSv3 and NFSv4 are difference. In NFSv3, client must rely on auxiliary protocol, t... See more...
Hi I got the answer from EMC technical engineer. [answer] It's expected. Since as for mount process, NFSv3 and NFSv4 are difference. In NFSv3, client must rely on auxiliary protocol, the mount protocol to request a list of server's exports and obtain root filehandle of a given export. And in NFSv4 uses the virtual file system to present the serer's export and associated root filehandles to the client. NFSv4 don't have mountd process during the mounting so the option mount access to sub directories disable will not limit access when using NFSv4.