14 Replies Latest reply on Feb 28, 2017 5:37 AM by Jan-Philipp Henkel

    HMC discovery fails with HMC version V8R8.6.0.0

    Bernard Stern

      Hello

       

      Our AIX admins are starting to upgrade the version/level of HMC software to V8R8.6.0.0 (from V8R8.4.0.1).

      The getMACAddresses Platform script is mandatory for scanning the device. With the new version, this script

      fails. My guess is that the output returned by the command 'netstat -ine' (the content of the getMACAddresses

      script) is slightly different between the 2 versions.

       

      V8R8.4.0.1:

       

      eth0  Link encap:Ethernet  HWaddr 6C:AE:8B:62:EF:92
            inet addr:NN.NN.NN.NN  Bcast:NN.NN.NN.NN  Mask:NN.NN.NN.NN
            inet6 addr: XXXXXXXXX Scope:Link
            UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
            RX packets:11313820 errors:0 dropped:0 overruns:0 frame:0
            TX packets:11467951 errors:0 dropped:0 overruns:0 carrier:0
            collisions:0 txqueuelen:1000
            RX bytes:2182383545 (2.0 GiB)  TX bytes:1600013167 (1.4 GiB)
            Memory:91a60000-91a80000

       

      V8R8.6.0.0

       

      eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500

              inet NN.NN.NN.NN  netmask NN.NN.NN.NN  broadcast NN.NN.NN.NN

              inet6 XXXXXXXXXXXX  prefixlen YY  scopeid 0x20<link>

              ether 34:40:b5:d4:88:88  txqueuelen 1000  (Ethernet)

              RX packets 15412  bytes 8634292 (8.2 MiB)

              RX errors 0  dropped 0  overruns 0  frame 0

              TX packets 14367  bytes 1991375 (1.8 MiB)

              TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

       

      In the older HMC version, you have HWaddr in the first line, wheras in the

      newer HMC version, the MAC address is in the 4th line at ether. Since we cannot

      change the output of the HMC command, we need the ADDM code to accomodate

      for the new HMC command output as well. Was is the fastest way to get this

      fix? Anybody experienced the same problem?

       

      Thanks.

       

      Bernard

       

        • 1. Re: HMC discovery fails with HMC version V8R8.6.0.0
          Andrew Waters

          Could you send me (you can PM) the full unmodified output of netstat -ine

          • 2. Re: HMC discovery fails with HMC version V8R8.6.0.0
            Thomas Schuhn

            Hello Andrew

             

            i work with bernhard

             

            hier is the unmodified output

             

            --------------------------------------

            [tideway@<addm-scanner-servername> ~]$ ssh addm@<servername> netstat -ine

            Kernel Interface table

            eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500

                    inet 10.255.255.1  netmask 255.255.255.0  broadcast 10.255.255.255

                    inet6 fe80::3640:b5ff:fed4:8888  prefixlen 64  scopeid 0x20<link>

                    ether 34:40:b5:d4:88:88  txqueuelen 1000  (Ethernet)

                    RX packets 15291  bytes 8614596 (8.2 MiB)

                    RX errors 0  dropped 0  overruns 0  frame 0

                    TX packets 14228  bytes 1970175 (1.8 MiB)

                    TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

             

            eth1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500

                    inet 10.126.30.11  netmask 255.255.255.0  broadcast 10.126.30.255

                    inet6 fe80::3640:b5ff:fed4:888a  prefixlen 64  scopeid 0x20<link>

                    ether 34:40:b5:d4:88:8a  txqueuelen 1000  (Ethernet)

                    RX packets 275942  bytes 75945403 (72.4 MiB)

                    RX errors 0  dropped 0  overruns 0  frame 0

                    TX packets 252117  bytes 73505420 (70.1 MiB)

                    TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

             

            eth2: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500

                    ether 6c:ae:8b:6b:64:40  txqueuelen 1000  (Ethernet)

                    RX packets 0  bytes 0 (0.0 B)

                    RX errors 0  dropped 0  overruns 0  frame 0

                    TX packets 0  bytes 0 (0.0 B)

                    TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

             

            eth3: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500

                    ether 6c:ae:8b:6b:64:42  txqueuelen 1000  (Ethernet)

                    RX packets 0  bytes 0 (0.0 B)

                    RX errors 0  dropped 0  overruns 0  frame 0

                    TX packets 0  bytes 0 (0.0 B)

                    TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

             

            lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536

                    inet 127.0.0.1  netmask 255.0.0.0

                    inet6 ::1  prefixlen 128  scopeid 0x10<host>

                    loop  txqueuelen 0  (Local Loopback)

                    RX packets 685817  bytes 801850569 (764.7 MiB)

                    RX errors 0  dropped 0  overruns 0  frame 0

                    TX packets 685817  bytes 801850569 (764.7 MiB)

                    TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

             

            sl0: flags=4305<UP,POINTOPOINT,RUNNING,NOARP,MULTICAST>  mtu 576

                    inet 10.253.0.1  netmask 255.255.0.0  destination 10.253.0.1

                    slip  txqueuelen 10  (Serial Line IP)

                    RX packets 0  bytes 0 (0.0 B)

                    RX errors 0  dropped 0  overruns 0  frame 0

                    TX packets 207  bytes 15881 (15.5 KiB)

                    TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

             

            usb0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500

                    inet6 fe80::3440:b5ff:fef9:7753  prefixlen 64  scopeid 0x20<link>

                    ether 36:40:b5:f9:77:53  txqueuelen 1000  (Ethernet)

                    RX packets 25576  bytes 1665321 (1.5 MiB)

                    RX errors 0  dropped 0  overruns 0  frame 0

                    TX packets 325  bytes 112786 (110.1 KiB)

                    TX errors 24  dropped 0 overruns 0  carrier 0  collisions 0

             

            [tideway@<addmscanner-name> ~]$

             

            ---------------------------

            • 3. Re: HMC discovery fails with HMC version V8R8.6.0.0
              Bernard Stern

              Hi Andrew,

               

              I mailed the output back on Thursday, but I just got a non delivery report... delivery expired, too old :-(

              Anyway, Thomas posted the output here. I have some additional information, maybe this can be helpful:

               

              V8R8.4.0.1:

              Linux hmc002 2.6.32-358.23.2.90.hmc7_4p.x86_64 #1 SMP Mon Jul 20 11:57:11 CDT 2015 x86_64 x86_64 x86_64 GNU/Linux

               

              V8R8.6.0.0

              Linux hmc004 3.10.0-229.20.1.el7_1.ibm.37.x86_64 #1 SMP Fri Aug 12 11:28:46 CDT 2016 x86_64 x86_64 x86_64 GNU/Linux

               

              They switched to the newer 3.10 kernel on the latest HMC software release our AIX guys are rolling out.

               

              Thanks

               

              Bernard

              • 4. Re: HMC discovery fails with HMC version V8R8.6.0.0
                Thomas Schuhn

                Hello Andrew

                 

                Does BMC have a solution to the problem?

                 

                With kind regards

                Thomas

                • 5. Re: HMC discovery fails with HMC version V8R8.6.0.0
                  Andrew Waters

                  11.1 patch 3 should fix this which is just appearing on EPD.

                  3 of 3 people found this helpful
                  • 6. Re: HMC discovery fails with HMC version V8R8.6.0.0
                    Bernard Stern

                    great new, I'll check it out next week.

                    • 7. Re: HMC discovery fails with HMC version V8R8.6.0.0
                      Thad Esser

                      I found this post because I was in the same situation.  I had just upgraded to 11.1.0.2 yesterday (which is when I found the issue), so I went ahead and upgraded to 11.1.0.3.  That fixed the problem for me.

                      • 8. Re: HMC discovery fails with HMC version V8R8.6.0.0
                        Bernard Stern

                        Hi Andrew, the latest patch 3 fixed the problem for me as well. Thanks to BMC for this quick resolution of that problem.

                        • 9. Re: HMC discovery fails with HMC version V8R8.6.0.0
                          Jan-Philipp Henkel

                          Hello Andrew

                           

                          We got a problem at 3 HMC devices, that they are marked as unsupported devices.

                          We running 11.1.0.3 with the latest TKU.

                           

                          The netstat info is:

                          :~> netstat -ine

                          Kernel Interface table

                          eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500

                                  inet 172.22.242.31  netmask 255.255.255.0  broadcast 172.22.242.255

                                  inet6 fe80::e61f:13ff:fee6:56e0  prefixlen 64  scopeid 0x20<link>

                                  ether e4:1f:13:e6:56:e0  txqueuelen 1000  (Ethernet)

                                  RX packets 97454371  bytes 27017952326 (25.1 GiB)

                                  RX errors 0  dropped 2856  overruns 0  frame 0

                                  TX packets 105171017  bytes 43317888967 (40.3 GiB)

                                  TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

                           

                          eth1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500

                                  inet 10.0.255.1  netmask 255.255.255.0  broadcast 10.0.255.255

                                  inet6 fe80::e61f:13ff:fee6:56e2  prefixlen 64  scopeid 0x20<link>

                                  ether e4:1f:13:e6:56:e2  txqueuelen 1000  (Ethernet)

                                  RX packets 2589647  bytes 1093881247 (1.0 GiB)

                                  RX errors 0  dropped 0  overruns 0  frame 0

                                  TX packets 2608428  bytes 329931170 (314.6 MiB)

                                  TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

                           

                          eth2: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500

                                  ether e4:1f:13:34:0e:18  txqueuelen 1000  (Ethernet)

                                  RX packets 0  bytes 0 (0.0 B)

                                  RX errors 0  dropped 0  overruns 0  frame 0

                                  TX packets 0  bytes 0 (0.0 B)

                                  TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

                           

                          eth3: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500

                                  ether e4:1f:13:34:0e:1a  txqueuelen 1000  (Ethernet)

                                  RX packets 0  bytes 0 (0.0 B)

                                  RX errors 0  dropped 0  overruns 0  frame 0

                                  TX packets 0  bytes 0 (0.0 B)

                                  TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

                           

                          lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536

                                  inet 127.0.0.1  netmask 255.0.0.0

                                  inet6 ::1  prefixlen 128  scopeid 0x10<host>

                                  loop  txqueuelen 0  (Local Loopback)

                                  RX packets 633515361  bytes 200527878419 (186.7 GiB)

                                  RX errors 0  dropped 0  overruns 0  frame 0

                                  TX packets 633515361  bytes 200527878419 (186.7 GiB)

                                  TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

                           

                          sl0: flags=4305<UP,POINTOPOINT,RUNNING,NOARP,MULTICAST>  mtu 576

                                  inet 10.253.0.1  netmask 255.255.0.0  destination 11.221.0.1

                                  slip  txqueuelen 10  (Serial Line IP)

                                  RX packets 0  bytes 0 (0.0 B)

                                  RX errors 0  dropped 0  overruns 0  frame 0

                                  TX packets 3000  bytes 230942 (225.5 KiB)

                                  TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

                                 

                          usb0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500

                                  inet6 fe80::e41f:13ff:fee8:44f7  prefixlen 64  scopeid 0x20<link>

                                  ether e6:1f:13:e8:44:f7  txqueuelen 1000  (Ethernet)

                                  RX packets 380322  bytes 24757310 (23.6 MiB)

                                  RX errors 0  dropped 0  overruns 0  frame 0

                                  TX packets 3166  bytes 1719764 (1.6 MiB)

                                  TX errors 107  dropped 0 overruns 0  carrier 0  collisions 0

                           

                           

                           

                          Is there hint for a solution?

                           

                          Please let us know.

                           

                          Thanks

                           

                          Best regards

                          Jan-Philipp

                          • 10. Re: HMC discovery fails with HMC version V8R8.6.0.0
                            Andrew Waters

                            If it is reporting an unsupported device I would not expect it to get as far as looking at the MAC addresses.

                             

                            What is the result of the getDeviceInfo accessible from the DiscoveryAccess page?

                            • 11. Re: HMC discovery fails with HMC version V8R8.6.0.0
                              Jan-Philipp Henkel

                              We get this info back from the green getDeviceInfo:

                              Discovery Method     getDeviceInfo

                              Discovery Duration     37

                              Request Time     28/02/2017 09:52 CET

                              Hostname     xxxx

                              Discovery Access     xxx.ccc.vvv.bbb @ 2017-02-28 08:52:14.107803+00:00

                              • 12. Re: HMC discovery fails with HMC version V8R8.6.0.0
                                Jan-Philipp Henkel

                                The session results told us that there is a problem by using the right ssh credential:

                                unix login     Not set     No     Failed to get login session

                                The problem arises at 3 HMC device. Only one is successfully scanned via the same SSH credential.

                                • 13. Re: HMC discovery fails with HMC version V8R8.6.0.0
                                  Andrew Waters

                                  I assume you have tested the ssh credential works on the other HMCs. Is the prompt in the shell different?

                                  • 14. Re: HMC discovery fails with HMC version V8R8.6.0.0
                                    Jan-Philipp Henkel

                                    Now all IP's are ok, the cause was that the firewall was closed, for some strange reasons.

                                    Thanks for your help and time!