8 Replies Latest reply on Sep 8, 2015 4:20 PM by wluther

    A few findings, after NPM 11.5 RC Upgrade...

    wluther

      Roughly 4 hours to upgrade from NPM 11.0 to NPM 11.5 RC.

       

      Below, are the basics for the environment

       

      3 servers (all VMs w/6CPUs, 32GB RAM, & 150GB+ storage)

      Orion products=NPM, NCM, NTA, ET, & Additional Poller

       

      Server1=Primary NPM, NCM server

      Server2=NTA, NCM, & Additional Poller

      Server3=DataBase

       

       

      Problems/Issues found so far:

      • Missing Logo (shows a black box whether the logo options are checked or unchecked)
      • New page resource, "Storage Forecast" (and possibly "Volume Forecast"), was added/loaded into default "Node Details" page, causing those pages to not load correctly, causing the pages to time out.
      • New web alerts failed to migrate all alerts (understanding some default alerts were going to fail anyway, we also had various custom advanced alerts fail)
      • Variable within various alerts either fail to show the values, show the variable instead of the value, or show an unformatted value, such as bandwidth in exponentials instead of converted values)
      • Most likely just an odd personal preference here, however, I am still baffled by the use of tiny windows, being unable to adjust their sizes... still...

       

      • Also, a few minutes ago, I was told that our guy that make our graphs in NPM, is no longer able to adjust column widths when using FireFox.  It appears he can still adjust using Chrome.

       

       

       

       

      • Missing Logo (shows a black box whether the logo options are checked or unchecked)

      There is simply a little black box in the corner where the logo would be.

      npm_11-5_rc_logo_space-001.PNG

       

      This box remains, whether the logo setting is checked or unchecked.

      npm_11-5_rc_web-console_logo_settings-001a.png

       

       

      • New page resource, "Storage Forecast" (and possibly "Volume Forecast"), was added/loaded into default "Node Details" page, causing those pages to not load correctly, causing the pages to time out.

      I opened a ticket with tech support, ticket #741777, where they were able to determine these new resources were causing the page timeouts.

      Support ended up removing these resources from all views.

      Afterwards, the pages loaded up without any issues.

      Removing these new resources does allow us to use our system again, however, a new feature you cannot use, is, well, not of any real use.

       

       

      • New web alerts

      This is what the alert emails looked like when received, before the upgrade to NPM11.5RC:

      npm_11-5_rc_alerts_bandwidth_readout-000a.png

       

      This is what those same alert emails look like now, after the upgrade:

      npm_11-5_rc_alerts_bandwidth_readout-001a.PNG

       

       

       

       

      On a side note, it would be nice to be able to click on these variables, allowing you to go back in to adjust them.

      npm_11-5_rc_alerts_bandwidth_readout-002a.png

       

       

       

      I would also like to see these alerts/alert variables better managed, now they are web based.

      The values, if I remember correctly, were able to be adjusted from the server based alert program, yet here, in the new web based alerts, it does not allow the advanced editing of ALL of them.

      npm_11-5_rc_alerts_bandwidth_readout-003a.png

       

      Some variables allow it, while others do not. (I do not recall as much work required with getting the converted data in the previous version, so it may simply be something I am overlooking...)

      Also, it would be nice if the conversion/formula would take the current percent utilization and convert it to the corresponding Gbps/Mbps/Kbps etc... (For the example image below, the number/value did not change at all, for any of the conversion options.)

      Previously, we were able to have the alert send out the current traffic value, in a readable format, for the interface(s).  Currently, there is either no option to do so, or I have simply not found it.

      npm_11-5_rc_alerts_bandwidth_readout-004a.png

       

       

       

       

       

       

       

      • Most likely just an odd personal preference here, however, I am still baffled by the use of tiny windows, being unable to adjust their sizes... still...

      I know I am probably the only one here that does not like to be contained in tiny little workspaces, but...PLEASE!!!!!!!!

      Please give me a way to use the space I have available. Scrollbars on tiny windows are the devil!!

      It would be so very very nice to be able to work within a window/space that had column widths auto adjusted, and workspaces either auto adjust as well, or just give us the option to adjust things, and then make sure to remember the settings so we do not have readjust them the next time.  Just think of all those nerds, with their desktop real estate starving and wasting away... don't punish them... it's not their fault...

      npm_11-5_rc_windows_sizes-001b.png

       

       

       

       

       

       

      If/When we come across any other issues, I will update this page accordingly.

       

      Thanks for all the help and hard work.

       

      -Will

        • Re: A few findings, after NPM 11.5 RC Upgrade...
          dfairles

          After Running config wizard again because of missing NTA resources I am getting timeouts now too.

           

           

          Missing logo Error:

           

          2015-01-13 14:25:43,392 [9] ERROR LogoImageHandler - Unexpected error trying to provide logo image for the page.

          System.FormatException: Invalid length for a Base-64 char array or string.

             at System.Convert.FromBase64_Decode(Char* startInputPtr, Int32 inputLength, Byte* startDestPtr, Int32 destLength)

             at System.Convert.FromBase64CharPtr(Char* inputPtr, Int32 inputLength)

             at System.Convert.FromBase64String(String s)

             at LogoImageHandler.ProcessRequest(HttpContext context)

          *** Assembly App_Web_y00maqg0, Version=0.0.0.0, Culture=neutral, PublicKeyToken=null, .NET version v4.0.30319 ***

          *** Assembly App_Web_mypht2vq, Version=0.0.0.0, Culture=neutral, PublicKeyToken=null, .NET version v4.0.30319 ***

          2015-01-13 14:37:13,440 [9] ERROR ASP.global_asax - Application_Error(1dee33047dbe43bcaaa2948595ba275c)

          System.Web.HttpException (0x80004005): Request timed out.

          2015-01-13 14:37:13,549 [31] ERROR LogoImageHandler - Unexpected error trying to provide logo image for the page.

          System.FormatException: Invalid length for a Base-64 char array or string.

             at System.Convert.FromBase64_Decode(Char* startInputPtr, Int32 inputLength, Byte* startDestPtr, Int32 destLength)

             at System.Convert.FromBase64CharPtr(Char* inputPtr, Int32 inputLength)

             at System.Convert.FromBase64String(String s)

             at LogoImageHandler.ProcessRequest(HttpContext context)

           

          NPM 11.5RC

          rob.hock

          • Re: A few findings, after NPM 11.5 RC Upgrade...
            jeremydr

            I agree with the tiny windowed section.

            • Re: A few findings, after NPM 11.5 RC Upgrade...
              Deltona

              Hi Will,

               

              Just wanted to add my 2c to the module sizing feedback.

              I too wish we could resize these modules, not because i have so much real estate but rather the opposite!

              When i'm working on systems with an 800x600 resolution and trying to access Orion, it is impossible to use the floating modules.

              So for that reason i wish the modules would adapt to screen resolution, and for that to happen, they must of course be resizeable.

              Once resizeable, everyone would benefit.

              • Re: A few findings, after NPM 11.5 RC Upgrade...
                damien.solodow

                I have a support case open on one issue we're having (errors when editing nodes) but have a few other issues around the new alert manager:

                 

                Our "you're low on disk space" alerts are reporting disk size in bytes rather than a more useful measure like MB or GB; and I'm not seeing a good way to convert.

                The other headache is we have an alert that we only want to trigger if the condition exists for 72 hours (don't ask) and the web based alert manager doesn't allow for a period of more than 60 minutes.

                • Re: A few findings, after NPM 11.5 RC Upgrade...
                  isantoro

                   

                  New web alerts:

                   

                  Did you ever find out about the email format?

                  It is causing me problems with the recipient of my alerts.

                   

                  Thank you.

                   

                    • Re: A few findings, after NPM 11.5 RC Upgrade...
                      wluther

                      isantoro

                      While we are currently using 11.5.2, and not 11.5 RC, this is how the I currently have our alert setup.

                       

                      Current traffic load of this interface is:
                      Received : ${Inbps as Bandwidth} / ${N=SwisEntity;M=InPercentUtil} % Utilization.
                      Transmitted : ${Outbps as Bandwidth} / ${N=SwisEntity;M=OutPercentUtil} % Utilization.
                      

                       

                      I ended up finding this on some other Thwack post.

                      This provides us with an acceptable solution.

                       

                      I hope it helps you too.

                       

                      Thank you,

                       

                      -Will