DX Infrastructure Manager

Expand all | Collapse all

GA Announcement: AIOps - Infrastructure Monitoring: CA UIM 9 Service Pack 1

  • 1.  GA Announcement: AIOps - Infrastructure Monitoring: CA UIM 9 Service Pack 1

    Posted 05-02-2019 02:46 AM
      |   view attached

    Excitingly announcing General Availability (GA) of CA Unified Infrastructure Management (UIM) version 9 Service Pack 1 aka UIM 9.1.0. Induction of Service Pack-I (SP1) leapfrogs the customer’s Monitoring experience to next level with regards to Ease of Use and Time to Value (TTV).

     

    Some salient Highlights from UIM 9.1.0: 

    • Theme: Data Security in Transit  

    To prevent any hacking attempt (Man in the middle attacks) of Open, Extensible UIM Architecture, introducing the Secure Bus. It provides complete encapsulation of data in transit within SSL encrypted tunnels. The additional layer of encryption doesn’t collect any performance Tax, still we are offering a choice in terms of 2 distinct Hub & Robot variants 9.10 with optional 9.10S [Secure].   

    • Theme: Availability at a Glance

    As asked by our 500+ community members providing the Enterprise level ‘Availability Report’. It can be consumed for both Group and Device level for all physical, virtual and leading cloud services. Availability gets Auto derived at runtime utilizing a combination of a device’s power state, reachability % age while taking cognizance of maintenance windows for accurate SLA compliance. 

    • Theme: Alarm Policy Inheritance

    Manage Many as one: via defining Alarm policies at a container group level with prioritized ranking. It’s Auto inherited by all the child groups and devices alike, Unless otherwise overridden by Admin. 

    • Theme: Data observability  

    Slice & dice Inventory, Alarm visualizations dynamically using rich filtering mechanisms. Also define your Dynamic group structure for 0-touch monitoring from Enhanced HTML5 based operator console.   

    • Theme: AI & Automation

    Augmented synergy with OI & NextGen APM platforms (deployed anywhere) by securely feeding Metrices, Alarms & Topology via Proxy. At the same time maintaining Bi-Directional synchronization regarding Actions taken anywhere. Enhanced self-remediation capabilities via native Webhook supporting multiple custom headers.

    • Theme: Modernization

    UIM 9.1.0 now supports newer monitoring platforms like Windows 2019, Debian 9 …etc. Truly as a Service Pack it includes defect fixes till date, along with many stability and performance improvements across all layers of deployment e.g. JRE 8u212, JasperReports® Server 7.1.1 for both bundled and external CABI et.al.

     

    Before you ask, here’s

     

    I recommend all customers’ to attend ‘Why UIM 9 and how to upgrade to UIM 9 SP1’ bright TALK webcast.

     

    Thank you again for your business

     

    - Ashish Aggarwal (aggas01)

     

    datsu01, sensu04 SandeepTiwary RajeevKurupati ghosu02 chumu01 garav01

    Attachment(s)



  • 2.  Re: GA Announcement: AIOps - Infrastructure Monitoring: CA UIM 9 Service Pack 1

    Posted 05-02-2019 02:32 PM

    Thanks Ashish. One thing I want to mention, point out here.

    If we don't use the 'secure' version of the robot/hub then should we delete the robot_update 7.10S / hub v7.10S entries from our archive.

    After the upgrade both entries were in my archive:

    • hub v9.10
    • hub v9.10S
    • robot_update v7.10
    • robot_update v7.10S 

    The issue here is that if you r-click on a controller and say "update" it will use the 7.10S as it thinks its a newer version and then I'm thinking that would cause issues.

    Would it be safe to say we should delete the hub & robot_update 7.10S entries out of our archive? Also should disable the distsrv probe forwarding rule before the installer so we can clean up this entry so that when it start it doens't sent this version out to other hubs that might use the "S" version and break things.

     



  • 3.  Re: GA Announcement: AIOps - Infrastructure Monitoring: CA UIM 9 Service Pack 1

    Posted 05-03-2019 05:00 AM

    We already have this documented https://docops.ca.com/pages/viewpage.action?pageId=537402514#SecureHubandRobot(CAUIM9SP1)-Considerations

    In IM, for components that have both secure (9.10S) and non-secure (9.10) packages in the archive, do not use the Update Version option to update the version. The reason is that the Update Version option always prompts you to update to the highest version number that is present in the archive. In this case, the highest version is 9.10S.

    Therefore, it prompts you to update to a secure version even when the version that you are updating is non-secure. For example, you want to update the non-secure robot (controller) version from 7.97 to 9.10.

     

    If you use Update Version, you get the option to update to 9.10S, which is the secure version. We recommend that you use the drag-and-drop or Distribute option to update the version.  

     

    pulra03



  • 4.  Re: GA Announcement: AIOps - Infrastructure Monitoring: CA UIM 9 Service Pack 1

    Posted 05-03-2019 09:54 AM

    Thanks Ashish. I just wanted to point this out even more for folks b/c its not always the end user who's doing the r-click update method that will mess up folks UIM environments. There are situations where machines will have scripts that will go out and ask for the latest robot update and then your environment is possibly broken with the "S" robot existing in the archive. Also probe super packs can also request latest robot version and then hit the situation. Also with distsrv forwarding rules in place all other hubs will get this update and you won't even know about it till the "S" version is deployed. For example in Citrix golden image setups where when a box is rebooted it gets the latest version of robot/probes from a local hub archive which usually isn't the primary hub.



  • 5.  Re: GA Announcement: AIOps - Infrastructure Monitoring: CA UIM 9 Service Pack 1

    Posted 05-03-2019 03:27 PM

    I'll come out and say that encoding product information in the version number is extremely bad form. I'm still dealing with the mess that CDM V6.10-MC created - or nas 9.0HF1 because 9.0HF1 sorts after 9.06.

     

    Now we essentially have two seperate robot packages and two seperate hub packages differentiated by an S in the version number. Why not have different names?

     

    Wouldn't hub_secure v9.10 and hub v9.10 have made more sense?

     

    Daniel, your problem will get "fixed" when they come out with the obligatory patch for hub v9.10 named v9.1HF1. probably shortly followed by v9.10SHF1 - or will it be V9.10HF1S - or V9.1HF1S. Sarcasm abounds here I think.

     

    And while I'm typing this, why does the documentation refer to this as 9.1 when the version string is 9.10 (nine dot ten) - the version string should have been 9.01. But then we already had 9.0.2.  But then in other places it's 9 SP1. distsrv separates on the first dot to get version and sub version and build is a seperate number. It then treats them as alphabetic strings for comparison purposes. It looks sloppy. And while it doesn't matter to me, when I fill out a form that asks for a version number, which do I use: 9.1, 9.10, or 9 SP1.



  • 6.  Re: GA Announcement: AIOps - Infrastructure Monitoring: CA UIM 9 Service Pack 1

    Posted 05-03-2019 07:36 AM

    Is a fresh install version of UIM 9.0.2 sp1 planned or will it always be a 2 step procedure (9.0.2 GA followed by the sp1)?

    Thanks, Luc



  • 7.  Re: GA Announcement: AIOps - Infrastructure Monitoring: CA UIM 9 Service Pack 1

    Posted 05-03-2019 09:55 AM

    +1. Yeah its not clear if you can go from 8.x to straight 9.1 or do you have to do the upgrade to 9.02 then 9.1.



  • 8.  Re: GA Announcement: AIOps - Infrastructure Monitoring: CA UIM 9 Service Pack 1

    Posted 05-03-2019 12:00 PM

    Hi as it is a service pack it will always require 9.02 be installed first

     

    the upgrade path is documented here https://docops.ca.com/ca-unified-infrastructure-management/9-0-2/en/installing/product-compatibility/supported-upgrade-paths

    regards

    Rich



  • 9.  Re: GA Announcement: AIOps - Infrastructure Monitoring: CA UIM 9 Service Pack 1

    Posted 05-07-2019 12:14 PM

    Not to question Broadcom's software versioning strategy but service packs usually don't increment a product's version number. 

     

    In the real world, one would expect that to install 9.1, one would not need to first install 9.0.2.

     

    Additionally, in the real world, down time costs money. So if one were running a currently supported version of a product, say 8.5.1, one would expect that moving to another newer supported version, say 9.1, it would be direct and as a result of that, minimizing the downtime. In this case, because it's not supported, one is forced to double their outage window. Double the cost.

     

    The additional thing that's interesting is that the installers for 9.1 are all slightly larger than their 9.0.2 counterparts - like everything is there but the lack of a direct install path is maybe just a stipulation and not a real requirement. 



  • 10.  Re: GA Announcement: AIOps - Infrastructure Monitoring: CA UIM 9 Service Pack 1

    Posted 05-07-2019 05:46 PM

    And not to harp on this a little more but the CM_NIMBUS_PACKAGE table only allows real values

     

    CREATE TABLE [dbo].[CM_NIMBUS_PACKAGE](
    [robot_id] [int] NOT NULL,
    [name] [varchar](256) NOT NULL,
    [version] [real] NOT NULL,
    [description] [varchar](255) NOT NULL,
    [install_time] [datetime] NOT NULL,
    CONSTRAINT [PK_CM_NIMBUS_PACKAGE] PRIMARY KEY CLUSTERED
    (
    [robot_id] ASC,
    [name] ASC
    )WITH (PAD_INDEX = OFF, STATISTICS_NORECOMPUTE = OFF, IGNORE_DUP_KEY = OFF, ALLOW_ROW_LOCKS = ON, ALLOW_PAGE_LOCKS = ON) ON [PRIMARY]
    ) ON [PRIMARY]

     

    It does look like discovery server strips off everything from the first non-numeric character to the end of the version string so the table is populated with at least something from these non-numeric version strings but this will result in an inability to determine the difference between hub 9.10 and 9.10S in this table. 



  • 11.  RE: GA Announcement: AIOps - Infrastructure Monitoring: CA UIM 9 Service Pack 1

    Posted 06-11-2019 11:14 PM
    An question about the synchronizing of UIM9SP1 and UMP HF2
    I have noticed that

    1.  UMP 9.0.2 Hotfix 2
        The cabi probe is updated to deploy CABI Server version 6.4.3
         https://docops.ca.com/ca-unified-infrastructure-management/9-0-2/en/release-notes/ump-9-0-2-hotfix-2
        UIM9SP1 
        The cabi probe 4.1.0 and cabi_external probe 4.1.0 are updated to deploy CABI Server version 7.1.1
         https://docops.ca.com/ca-unified-infrastructure-management/9-0-2/en/release-notes/ca-uim-9-service-pack-1#CAUIM9ServicePack1-cabi_jasperCABIProbesDeployCABIJasperReportsServer7.1.1

    2.  UIM 9 SP1  does not cover the fix of UMP9.0.2 Hotfix2
          https://docops.ca.com/ca-unified-infrastructure-management/9-0-2/en/release-notes/ump-9-0-2-hotfix-2
          https://docops.ca.com/ca-unified-infrastructure-management/9-0-2/en/release-notes/resolved-issues

    So the upgrade path , like UIM8.5.1 ->UIM9.0.2 ->UIM9SP1,  how to do with  UMP9.0.2HF2?
    What would it be if  UMP9.0.2HF2 -> UIM9SP1, does it work?



  • 12.  RE: GA Announcement: AIOps - Infrastructure Monitoring: CA UIM 9 Service Pack 1

    Posted 06-12-2019 01:37 AM
    From what's new sp1: "As part of the regular release cycle for updating CA UIM 9.0.2, we are pleased to announce CA UIM 9 Service Pack 1 (SP1). CA UIM 9 SP1 includes new and enhanced features, various vulnerability fixes, resolved customer issues, UMP 9.0.2 HF2 functionality, and so on."