Cisco Unified Communications Manager 14 EOL and 15 Upgrade tips slides from Cisco Live
Hello all! I'm sure some of you are at Cisco Live NAM right now, but if you aren't, there was a great presentation on CUCM. CentOS is being swapped out, CUCM 15 appears to be switching to Python 3, along with other security changes. They've announced an EOL date for CUCM 14 as well. Take a look at the slide deck as it's very interesting. Their product team also informed me that the API is unchanged from v12.5 through CUCM 15, so our integration should continue to work. Please let us know if you have any issues with the latest version of our PowerPack and CUCM 15.
How to Fix powershell communication error?
How to Fix powershell communication error Forward and reverse name resolution is not properly configured for server? We have multiple windows server in which we are facing this issue and server have multiple DNS entries and we can delete them. also i tried to add IP and host in sciencelogic data collector also added in dnsmsaq-resolve.conf to resolve this issue but still we are facing this error Forward and reverse name resolution is not properly configured for server, how to fix this issue without deleting DNS entries.SL1 Certifications Overview Guide
Our certification paths are aligned to ScienceLogic SL1 version 12.1/Golden Gate and cater to the expressed needs of our valued customers, ensuring that our training meets your evolving requirements. Whether you're a current ScienceLogic customer or new to our platform, we encourage you to embark on these refreshed certification paths. Benefits of the ScienceLogic Certification • Current, relevant content aligned with your needs. • Leverage the power of the SL1 platform more effectively. • Gain insights into the latest functionality of 12.1, including PowerPacks, Guided Discovery, Device Investigator and Event Insights. Learn more about our Professional and Expert Certification Paths.How will the Hollywood update affect AI insights and the SL1 platform?
Explore everything about the SL1 12.2 Hollywood release with this learning track which includes a press release, solution sheet, on-demand webinar, and more. Explore how our AIOps platform, SL1, harnesses the immense power of artificial intelligence (AI) and machine learning (ML) to empower IT teams with human-ready root cause analysis. See how SL1 shows real-world examples of how our actionable insights enable IT teams to rapidly pinpoint anomalies and their root causes, auto-remediate issues, and work 10X more efficiently. After reviewing these resources, you’ll understand howScienceLogic SL1: Delivers human-ready AI insights using generative AI Helps filter out the noise using AI/ML Unlocks operational efficiencies with automation I also encourage you to check out the 12.2 release notes and documentation for a deeper dive into the Hollywood release.Tips for How to Optimize your SL1 System
ScienceLogic SL1 is a very powerful system that can make the lives of your operations staff easier, but those outcomes require some maintenance and optimizations. Read on for a few tips about how to get the most out of your SL1 System 1. Use Event Insights You probably know that Event Insights (Expand left menu -> Events -> Event Insights) is a powerful view to see how SL1 is reducing noise in your system, but did you know that it helps you see potential optimizations also? On the right side of the Event Insights page there is a section called “Tuning Targets”. By looking at what devices are creating the most events and which event policies are resulting in the most events, you can see actions that you can take to clean things up. In the example screenshot above, I would want to look at device 203.0.113.249 to see what is going on to trigger so many events. It could be a misconfiguration on the system, a hardware issue that needs to be remedied, or a threshold that could be tweaked. The lower section shows event policies that are being triggered the most. Noise-reduction options here include requiring multiple triggers within a time frame to be sure that the events are persisting, suppressing the events for test or dev devices, or tweaking thresholds to be sure that the event reflects an actionable problem to fix. 2. Use Operational Insights Operational Insights is a powerpack built by ScienceLogic to help manage your SL1 stack. There are separate versions for self-hosted and SaaS customers, but most of the functionality is the same. Once it’s installed and configured, it presents data on a series of dashboards. These dashboards can help you see the status of your collectors, keep track of the trends in the number of devices discovered and business services configured, and even keep an eye on under-the-hood metrics like Configuration Push time and the Event processing backlog. 3. Daily Health Tasks Did you know that the SL1 Documentation has a list ofdaily health tasks? Some of these items are covered by Event Insights and Operational Insights, but some are not. For example, it’s a great idea to check the System Logs periodically to make sure you know how things are running. If you have concerns about other items in the “Healthy SL1 System” table, you can set event policies and automations to make sure that you are notified in case of any issues. 4. Join the ScienceLogic Nexus Community! Finally, the ScienceLogic Nexus Community is a great resource to keep things working at your best. Interacting with fellow customers, submitting enhancement ideas to the Product Management team, and keeping up with the latest information on new releases helps you plan appropriately and use your time and energy well. To get started: Register with the Nexus Community (its easy) Visit ourCommunity Information Forum for assistance and tips Thanks for your time and I would love to see some feedback and ideas for topics of interest.
Welcome to the ScienceLogic SL1 Discussion Forum
We would like to welcome you to this forum where you can participate in open collaboration and meaningful discussions about all things SL1. The purpose of this area is to foster collaboration about ScienceLogic SL1 topics and ideas and for you to find solutions. As a community of IT professionals, we're always eager to learn new things and improve our skills. In this forum you can find people with similar ideas and challenges who can help you learn and be inspired. We hope you look forward to participating in these discussions and contributing to the community. Cheers to fostering connections, sharing insights, and driving the future of AIOps together. The ScienceLogic Community Team
How can the next device ID to be allocated be changed in SL1?
Our automated SL1/PowerFlow testing process involves creating new devices in SL1. We regularly clone ITSM/CMDB envs into the test environment and the issue is these envs have SL1 device IDs far in advance of the test SL1. This causes test breakage when creating a new SL1 device because some other device is more likely already in existence in the ITSM/CMDB. If the device ID difference range was only small then repeated dummy device creations works a treat but when the difference is in the thousands, this technique is not very useful. Is it possible to change the "next" device ID SL1 uses to create a new device? We would then be able to bring the test SL1 device ID into alignment with the cloned ITSM/CMDB. How can the device ID bump be performed programatically as ideally the entire ITSM/CMDB cloning process should be automated. Thanks, Michael
