Node Navigation
Recent Content
SL1: System Upgrade Assessment v100 PowerPack Release Notification
We are pleased to announce that the SL1: System Upgrade Assessment v100 PowerPack has been released. The download for this release can be found on the Support Portal under the PowerPack filename: https://support.sciencelogic.com/s/release-version/aBuVL0000000Uu90AE/sl1-system-upgrade-assessment The following enhancements and addressed issues are included this release of the SL1: System Upgrade Assessment v100 PowerPack: The System Upgrade Assessment PowerPack version 100 includes the following features: - A "Python Assessment Tool" report tool that identifies which PowerPacks will need to be rebuilt before upgrading to a newer SL1 version. - A "PowerPack Encryption Validation" report tool that identifies which PowerPacks need to be rebuilt before upgrading SL1 to version 12.2.2 or above. Please refer to the SL1: System Upgrade Assessment v100 PowerPack File Details in the PowerPacks section of the Support Portal for all information pertaining to the SL1: System Upgrade Assessment v100 PowerPack Support Status, Minimum SL1 Version, Solution Information, and Pricing Information. The SL1: System Upgrade Assessment v100 PowerPack Release File Details also contains links to the Release Notes, Manual, and PowerPack Info Report. Issues Addressed in the SL1: System Upgrade Assessment v100 PowerPack Release can be found in the Release Notes.22Views1like2CommentsSL1 Data collector number of network adapters
How many network adapter is supported. Currently we have migrating between datacenters and due to ACI we cannot have vrf leaking. So we need 3 network adapters to cover all requirements. can someone advice? Currently we have 2 just for info.6Views0likes0CommentsAutomatic update of IP on Meraki assets
We are currently facing a scenario where the IP address of our Meraki devices changes upon reboot, which subsequently triggers a DFA alert. To streamline our operations and reduce manual intervention, we are exploring the possibility of capturing these IP changes and updating them automatically in SL. Meraki assets are onboarded through SNMP.7Views0likes1Comment- 18Views1like2Comments
Tech Connect Phoenix Agenda Oct 17th
In the Phoenix area this week? If you haven't already registered, it's not too late!!! We would love to see you at our Tech Connect event. Agenda Highlights ScienceLogic Product Roadmap CPO- Michael Nappi SL1 Studio: Device Onboarding made easy Sr. Director Engineering- Bill Rachilla Fundamentals of SL1 PowerFlow Automation Director Technical Marketing- Patrick Hubbard How to Unlock Your Full Potential and Get the Most Out of ScienceLogic Director Technical Marketing- Patrick Hubbard Service-Centric Operations: Best Practices to Get Started and Transform IT Operations Sr. Director GSE Lee Koeping Using Generative AI to Shape the Future of AIOps and Observability CPO- Michael Nappi Full Agenda Register Now3Views1like0CommentsWant some Swag??? Call out for Content Requests, Ideas and Feedback
Call out for content ideas: What types of content would you find the most interesting in the Nexus Community? In previous communities I have had good success with shared documents where all members can contribute- Topics included: Favorite Resources- inks to other sites, learning and content)- the limitations are that they are public and no fee is required to access the links. Tech Tips- working document where members can each add tips that they think help with different stages of working with the product (Implementation, Maintenance etc. Center of Excellence- working document where members share governance and business practices that help their organizations use this and other technology successfully. We were hoping you could weigh in on your thoughts about ways you would like to be highlighted in the community and resources you would like to see. In return we will send some swag to the members with the 5 new ideas with the most likes over the next 30 days. Thank you, The Nexus Community Team31Views0likes1CommentThis week's updates to the Doc sites at docs.sciencelogic.com
10/11/24: Doc updates to the release notes site at https://docs.sciencelogic.com/release_notes_html/ Added release notes for the NVIDIAGPU PowerPack v100. Added release notes for the SL1: System Upgrade Assessment PowerPack v100. Updated the release notes for the Restorepoint MR20241010 release. 10/11/24 Doc updates to the main docs site at https://docs.sciencelogic.com/ Added a manual for the NVIDIAGPU PowerPack v100. Added a manual for the SL1: System Upgrade Assessment PowerPack v100. Updated the manual for the Restorepoint MR20241010 release.9Views3likes0CommentsNVIDIA: GPU Monitoring v100 PowerPack Release Notification
We are pleased to announce that the NVIDIA: GPU Monitoring v100 PowerPack has been released. The download for this release can be found on the Support Portal under the PowerPack filename: https://support.sciencelogic.com/s/release-version/aBuVL0000000V2D0AU/nvidia-gpu-monitoring The following enhancements and addressed issues are included this release of the NVIDIA: GPU Monitoring v100 PowerPack: The following Dynamic Applications that discover and collect data from NVIDIAGPU: Nvidia: Card Configuration Nvidia:Card Performance Nvidia: Memory Performance Event Policies and corresponding alerts that are triggered when NVIDIAGPU devices meet certain status criteria A sample SSH Credential ("Nvidia GPUMonitoring - Example") that you can use to create your own NVIDIA Credential A Device Template ("Nvidia GPUMonitor Template") that aligns NVIDIA Dynamic Applications with devices https://support.sciencelogic.com/s/release-version/aBuVL0000000V2D0AU/nvidia-gpu-monitoringn issue with OAuth2 authentication that prevented proxy credentials from functioning correctly. Please refer to the NVIDIA: GPU Monitoring v100 PowerPack File Details in the PowerPacks section of the Support Portal for all information pertaining to the NVIDIA: GPU Monitoring v100 PowerPack Support Status, Minimum SL1 Version, Solution Information, and Pricing Information. The NVIDIA: GPU Monitoring v100 PowerPack Release File Details also contains links to the Release Notes, Manual, and PowerPack Info Report. Issues Addressed in the NVIDIA: GPU Monitoring v100 PowerPack Release can be found in the Release Notes.4Views1like0CommentsNexus Community Member Roles and Ranks
Nexus- our ScienceLogic Community is comprised of many different types of members. We have different ways to identify and reward different participants based on who they are and their activities. Role- who the member is (Employee, Partner, Customer, Prospect) Rank- levels of members based on accumulated points and recognition, members move up as they participate more Role We have image/icons for employee members of the community so that you may more easily identify them: Ranks Nexus community members go up in ranks based on participation. Here are some of the participation activities we measure. Note that all require login to be tracked. Message and Content Views Posting a question, idea or other piece of content Commenting on a question, idea, blog or other piece of content ‘Liking’ content Here is our ranking system with the newest members starting at the bottom. Thanks for looking and as always- feel free to share your questions.12Views2likes0CommentsAzure subscription monitoring max retries error
Hi all, We are in the process of setting up SL1 to monitor a mix of Azure and on-prem VMWare devices. The Azure subscription monitors repeatedly error with: "Azure: Network Failure on App: ARMVMPerformance, Message: HTTPSConnectionPool(host='management.azure.com', port=443): Max retries exceeded with url: Failed to establish a new connection: [Errno -2] Name or service not known',)),". We have 14 subscriptions setup and some don't show the error at all, some show it weekly and 1 shows it every 15 minutes generating 1000's of critical alerts a month. SL1 support/PS say it is down to a DNS issue: We have checked with the ENG Team and it looks like a random DNS issue where it can't resolve "management.azure.com" from the collector and it looks transient. The error message points to a failure to resolve the hostname when the config da’s are run. However we use the same DNS server for all collectors and some subscriptions don't see the error. I can also do successful nslookups/pings/nmaps from the collectors. Has anyone seen something like this before? Thanks, Mark41Views4likes4Comments