Node Navigation
Recent Content
Week of January 27, 2025 - Latest KB Articles and Known Issues
1 MIN READ A set of Knowledgebase Articles published last week is listed below. All KBAs can be searched via Global Search on the Support Portal and filtered by various components like product release.PavaniKatkuri16 hours agoPlace Latest KB Articles and Known Issues BlogLatest KB Articles and Known Issues BlogModerator15Views0likes0CommentsSL1 Ibiza 12.3.1 Release Notification
We are pleased to announce that SL1 Ibiza 12.3.1 is now available. The release and documentation can be accessed using the following links: .iso: https://support.sciencelogic.com/s/release-file/aBtVL0000000n7B0AQ/1231 .siloupdate: https://support.sciencelogic.com/s/release-file/aBtVL0000000n8n0AA/1231 If you are planning to upgrade to SL1 Ibiza 12.3.1, be advised of the following: You can upgrade to this release directly from SL1 12.2.1.1, 12.2.1.2, 12.2.3, 12.2.4.1, 12.2.5, 12.2.6, and 12.3.0. You can also upgrade directly from SL1 12.1.2 if all of your SL1 appliances have been converted to OL8. If you are already on 12.1.2, you should upgrade directly to 12.3.1 without consuming the 12.2.x releases. If you are on 12.1.0.2 or 12.1.1, you should upgrade to 12.1.2, convert to OL8, and then upgrade directly to 12.3.1. STIG-compliant users can deploy this release; 12.2.x and 12.3.0 STIG-compliant users can upgrade to this release. Users who are on an 11.x MUD system cannot upgrade to this release; they must first follow the approved conversion process from 11.x MUD to 12.2.1.1 STIG. For more information, see the section on STIG Support. AWS deployments that are using Aurora 3 can upgrade to this release. If you are currently deployed using Aurora 2, you can upgrade to this release but must perform a post-upgrade Aurora 2 to 3 conversion. SL1 12.3.1 is Department of Defense Information Network (DoDIN)-certified. For more information, see the Sl1 Ibiza 12.3.1 release notes: https://docs.sciencelogic.com/release_notes/sciencelogic_12-3-1_release_notes.pdf11Views0likes0CommentsNexus Community Tip: How to mark your question as ‘Solved’
Hello Nexus Community Members, An important part of online communities is making sure that members’ questions are promptly answered & marked as solved. This helps in a variety of ways Members who are following your thread are alerted that you have resolved your question. This is helpful if they have the same question because they can review the response and apply as needed to their own implementation. Experts who are looking to help solve problems have visual indicator that this no longer needs their assistance. Whomever has responded with the correct answer gets credit for their time and efforts to help solve your problem. SLA’s in the community are met which is very important to our staff. Who can mark a question as solved? The OP (Original Poster) Moderators Community Manager Ideally the OP marks the thread as solved because ultimately, they know if the response is the correct or if more assistance is needed. Whomever marks the post as solved gets credit for that action and they move up in our Nexus Community Roles and Ranking system. We want our community members to have as much positive recognition as possible. Here is how you mark your Question/Thread as Resolved Login Go to your Question/Thread- there are two primary ways to do this- if you have Bookmarked it or via your Profile ‘Contributions’ feed. Once you are on the Question/Thread page review the responses If a response is correct, please click on the ‘Mark as Solution’ link on the left lower side of that response. If none of the responses resolve your question it is helpful if you post an update that you still need more assistance and include any pertinent details. You can also @mention people who responded or other community members to prompt them to visit your thread and assist. Thanks for your participation, Nexus Community Team6Views0likes0CommentsCelebrating Our Top Nexus Community Contributors – January Edition
We wanted to take a moment to recognize and say thank you to our incredible Nexus community members who made the biggest impact in January. Your participation, expertise, and willingness to share knowledge help this community grow and continue to provide value to all our customers. 🌟 A Huge Thank You to Our Top Contributors! 🌟 Whether you shared insights, answered questions, or provided helpful feedback, your contributions didn’t go unnoticed. This community thrives because of engaged members like you who bring their expertise and passion to the table. Why Your Contributions Matter Every post, discussion, and shared solution helps someone else find answers, learn something new, or improve their experience. This community wouldn’t be the same without your dedication and involvement! 💬 Here’s who inspired us the most in January: Most Page Views teppotahkapaa closely followed by @LukeLukeAuxilion Most Replies- we have a tie teppotahkapaa & Colin Most Idea Votes Given- we have a tie teppotahkapaa & Saskia Most Idea Votes Received robwight closely followed by deepakchopra99 🚀 Let’s Keep the Momentum Going! 🚀 We encourage everyone to stay active, share insights, and continue making this space a go-to resource. If you’re new here, don’t hesitate to jump in—your voice matters! Once again, thank you for making January such a fantastic month. We can’t wait to see what we accomplish together in the coming months! Best Regards, The Nexus Community Team22Views0likes0CommentsThis week's updates to the Doc sites at docs.sciencelogic.com
2/7/25 Doc Updates to the release notes site at https://docs.sciencelogic.com/release_notes_html/ Updates to the Restorepoint MR20250203 hotfix addressed a support defect for agents that crashed after updating. Skylar Analytics 1.2 release notes Datacenter Automation Utilities PowerPack 201 release notes Linux SSH Automations PowerPack v107 release notes Juniper Mist PowerPack v100.1 release notes 2/7/25 Doc updates to the main docs site at https://docs.sciencelogic.com/ Skylar Analytics 1.2 manual Updated Using Single Sign-On manual to include a note clarifying you might need to enter the complete URL displayed in the SAML trace for the attribute mapping fields. Added an icon and a link to the Restorepoint Developer Docs to the home page Linux SSH Automations PowerPack v107 manual Added a new SL1 Automation PowerPacks page, with a new icon and link on the home page as well Juniper Mist PowerPack v100.1 manual5Views1like0CommentsDatacenter Automation Utilities v201 PowerPack Release Notification
We are pleased to announce that the Datacenter Automation Utilities v201 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/aBu0z000000XZiBCAW/datacenter-automation-utilities The following enhancements and addressed issues are included in version 201 of the "Datacenter Automation Utilities" PowerPack: Addressed an issue that was preventing the run book actions in this PowerPack from working properly with the SL1 agent. The updates for this issue are supported on SL1 12.3.1 or later. NOTE: If this is a new installation of this PowerPack, you will need to enable all automation policies in the PowerPack before you can use them. NOTE: The Monitoring Guide needed no update from previous v200 so v200 is included here. Please refer to the Datacenter Automation Utilities v201 PowerPack File Details in the PowerPacks section of the Support Portal for all information pertaining to the Datacenter Automation Utilities v201 PowerPack Support Status, Minimum SL1 Version, Solution Information, and Pricing Information. The Datacenter Automation Utilities v201 PowerPack Release File Details also contains links to the Release Notes, Manual, and PowerPack Info Report. Issues Addressed in the Datacenter Automation Utilities v201 PowerPack Release can be found in the Release Notes6Views1like0CommentsLinux SSH Automations v107 Py3 PowerPack Release Notification
We are pleased to announce that the Linux SSH Automations v107 Py3 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/aBu0z000000XZipCAG/linux-ssh-automations Enhancements and Issues Addressed The following enhancements and addressed issues are included this release: Made updates to make the PowerPack compatible with Python 3, including updates to the libraries and execution environments for Python 3.6. The PowerPack now includes the following automation policies, and each Policy Type was updated to Active Events/User Initiated: Linux SSH: Illicit Process Remediation Linux SSH: Process Restart Remediation Linux SSH: Run CPU Diagnostic Commands Linux SSH: Run File System Diagnostic Commands Linux SSH: Run Interface Error/Discard Diagnostic Commands Linux SSH: Run Interface Utilization Diagnostic Commands Linux SSH: Run Memory/Swap Diagnostic Commands Linux SSH: Run System-Storage Diagnostic Commands NOTE: All automation policies in the PowerPack are disabled by default and must be enabled for use. NOTE: All automation policies in this PowerPack require the target device to be part of the "Linux Automation" device group. The PowerPack now includes the following run book actions: Linux CPU Diagnostic Commands Linux File System Diagnostic Commands Linux Illicit Process Remediation Linux Interface Error/Discard Diagnostic Commands Linux Interface Utilization Diagnostic Linux Memory Dmidecode Command Linux Memory/Swap Diagnostic Commands Linux Process Restart Remediation Linux System-Storage Diagnostic Commands Linux Tcpdump Command Added the following parameter to the "Execute Shell Commands" action type (version 2.2): dynamic_app_guid:Specifies the globally unique ID number (GUID) assigned to the Dynamic Application by SL1. You can specify multiple Dynamic Application IDs, separated by commas. If the credential_id parameter is not specified, SL1 will use the dynamic_app_guid parameter to determine the credential. If this value is not specified, or if it is an empty string, SL1 runs a query against the database to get the credential details. The default value for this parameter corresponds to the GUID value in the "Linux: Configuration Discovery" Dynamic Application. Enabled passwordless sudo access on the client being monitored to ensure that run book automations that use sudo in the commands work as expected. For more information, see the "Configuring Linux Devices" topic in the Linux SSH Automations PowerPack manual. Removed the write_password_after_command parameter from the "Execute Shell Commands" custom action type. Please refer to the Linux SSH Automations v107 Py3 PowerPack File Details in the PowerPacks section of the Support Portal for all information pertaining to the Linux SSH Automations v107 Py3 PowerPack Support Status, Minimum SL1 Version, Solution Information, and Pricing Information. The Linux SSH Automations v107 Py3 PowerPack Release File Details also contains links to the Release Notes, Manual, and PowerPack Info Report. Issues Addressed in the Linux SSH Automations v107 Py3 PowerPack Release can be found in the Release Notes6Views1like0CommentsJuniper Mist v100.1 PowerPack Release Notification
We are pleased to announce that the Juniper Mist v100.1 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/aBuVL0000000b1B0AQ/juniper-mist The following enhancements and addressed issues are included this release for Juniper Mist: Added support for collection using a proxy to the PowerPack. For more information about using a proxy, see the Juniper: Mist manual.. Added a divide by zero check to the "Memory Utilization" presentation object in the "Mist: AP Statistics" Dynamic Application. Please refer to the Juniper Mist v100.1 PowerPack File Details in the PowerPacks section of the Support Portal for all information pertaining to the Juniper Mist v100.1 PowerPack Support Status, Minimum SL1 Version, Solution Information, and Pricing Information. The Juniper Mist v100.1 PowerPack Release File Details also contains links to the Release Notes, Manual, and PowerPack Info Report. Issues Addressed in the Juniper Mist v100.1 PowerPack Release can be found in the Release Notes9Views0likes0CommentsThis week's updates to the Doc sites at docs.sciencelogic.com
1/31/25 Doc updates to the main docs site at https://docs.sciencelogic.com/ Updates to the Docker PowerPack manual to support changes from version 108 Updates to the HPE: Edge Connect (Silver Peak) PowerPack manual to support changes from version 200. 1/31/25 Doc Updates to the release notes site at https://docs.sciencelogic.com/release_notes_html/ Docker v108 PowerPack which updates the PowerPack to make it compatible with Python 3, addresses an issue with the "Docker: Host Device Class Realignment" run book action, and adds a device template to use if Dynamic Applications fail to align automatically during discovery. HPE: Edge Connect (Silver Peak) v200 PowerPack, which updates the PowerPack to Python 3, adds multiple Dynamic Applications, and adds a new example credential.7Views0likes0CommentsHPE Edge Connect (Silver Peak) v200 Py3 PowerPack Release Notification
We are pleased to announce that the HPE Edge Connect v200 Py3 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/aBu0z000000XZaHCAW/hpe-edge-connect-silver-peak Enhancements and Issues Addressed: Updated the PowerPack to be compatible with Python 3 Converted all Dynamic Applications to Python 3. Added two new Dynamic Applications to the PowerPack: HPE: Edge Connect Appliance Memory Performance HPE: Edge Connect Appliance CPU Performance NOTE: Both of the "HPE: Edge Connect Appliance Memory Performance" and "HPE: Edge Connect Appliance CPU Performance" Dynamic Applications are disabled by default. Enabling the "HPE: Edge Connect Appliance CPU Performance" Dynamic Application may cause performance issues on the orchestrator due to the Dynamic Application calling the API for each appliance device. Removed the "REST: Performance Monitor" Dynamic Application from the PowerPack, as it is not compatible with the Snippet Framework. IMPORTANT: Before upgrading to version 200 of the PowerPack, ScienceLogic recommends unaligning the "REST: Performance Monitor" Dynamic Application from existing root virtual devices. Added the new "HPE: Edge Connect v200 API Key" UCF subtype to the PowerPack. Added the new "HPE: Edge Connect API Key Example (UCF)" example credential to the PowerPack. Added a function to the snippet of each Dynamic Application in the PowerPack that checks for an API token in the headers. If one is found, you will receive a warning that instructs you to move the token to the "Embedded Password [%P]" field. NOTE: ScienceLogic does not recommend storing tokens in plain text fields, as this goes against security best practices. Please refer to the HPE Edge Connect v200 Py3 PowerPack File Details in the PowerPacks section of the Support Portal for all information pertaining to the HPE Edge Connect v200 Py3 PowerPack Support Status, Minimum SL1 Version, Solution Information, and Pricing Information. The HPE Edge Connect v200 Py3 PowerPack Release File Details also contains links to the Release Notes, Manual, and PowerPack Info Report. Issues Addressed in the HPE Edge Connect v200 Py3 PowerPack Release can be found in the Release Notes.7Views0likes0CommentsDocker v108 Py3 PowerPack Release Notification
We are pleased to announce that the Docker v108 Py3 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/aBu0z000000XZalCAG/docker The following enhancements and addressed issues are included this release: Updated the PowerPack to be compatible with Python 3.6 (SOL-27653) Addressed an issue that caused the "Docker: Host Device Class Realignment" run book action to activate incorrectly in certain situations. As part of the fix for this issue: The "Docker: Hosts and Swarm Cluster realignment to CU id of the leader node" event policy will only be triggered by the leader node. If one or more nodes are not discovered, they will not be taken into account when deciding whether to trigger the event. The run book action now uses the IP address instead of the hostname to read the cache, because the cache is saved using the IP address. (Case: 00424553) (SOL-27032) Added the "Docker Template Example" device template that you can apply to root (Docker Host) Docker devices if the required Dynamic Applications fail to align automatically during discovery. (SOL-1427) Made several modifications to example credentials in the PowerPack. Please refer to the Docker v108 Py3 PowerPack File Details in the PowerPacks section of the Support Portal for all information pertaining to the Docker v108 Py3 PowerPack Support Status, Minimum SL1 Version, Solution Information, and Pricing Information. The Docker v108 Py3 PowerPack Release File Details also contains links to the Release Notes, Manual, and PowerPack Info Report. Issues Addressed in the Docker v108 Py3 PowerPack Release can be found in the Release Notes.13Views0likes0Comments