Node Navigation
Recent Content
Cisco: Wireless v105 Py3 PowerPack Release Notification
We are pleased to announce that the Cisco: Wireless v105 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/aBu0z000000XZMBCA4/cisco-wireless Enhancements and Issues Addressed The following enhancements and addressed issues are included in this release: The PowerPack was updated for Python 3.6 compatibility. The Collector Affinity was set to Root device collector in all the Dynamic Applications. The "Cisco: WLC AP Config" Dynamic Application was updated to address an issue in which the MAC Addresses collection objects stored using a space instead of semicolon. Please refer to the Cisco: Wireless v105 Py3 PowerPack File Details in the PowerPacks section of the Support Portal for all information pertaining to the Cisco: Wireless v105 Py3 PowerPack Support Status, Minimum SL1 Version, Solution Information, and Pricing Information. The Cisco: Wireless v105 Py3 PowerPack Release File Details also contains links to the Release Notes, Manual, and PowerPack Info Report. Issues Addressed in the Cisco: Wireless v105 Py3 PowerPack Release can be found in the Release Notes4Views0likes0CommentsAzure monitoring and integration with CMDB
When gathering information from cloud stuff, or actually doing whatever with cloud staff you most often need the object's ID, that long hexastring. That same ID is also most used identifier and required information when trying to sync those cloud "devices" into ServiceNow CMDB. The issue is that SL1 Azure PP does not gather that information too much, one device class that we have so far found it is those actual VMs in cloud. But one could say that those are the only "devices" where it is easily found. So my question is, how you have planned, or done, the CMDB integration of Azure cloud stuff. Or have you done any automation from SL1 to Azure, because also there one always(?) need that object ID. I could have written also an Idea for this, but at least for me, Nexus does not support my ideas.Solved102Views1like2CommentsCisco 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.Solved1.3KViews2likes1CommentDell EMC: Unity v103 Py3 PowerPack Release Notification
We are pleased to announce that the Dell EMC: Unity v103 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/aBu0z000000XZWoCAO/dell-emc-unity Enhancements and Issues Addressed The following enhancements and addressed issues are included in this release: Updated the PowerPack for Python 3.6-compatibility using Snippet Framework. Added the "Dell EMC: Unity Example SF" universal example credential. Removed the following "Dell EMC: Unity LUN Discovery" Dynamic Application collection objects, as the "Dell EMC: Unity LUN Config" Dynamic Application collects the same information: Current Owner Default Owner Health State LUN Size LUN Type Thin Tiering Policy Updated the Collector Affinity to assigned collector in all Dynamic Applications. Updated the "Dell EMC: Unity Classify Root Device Class" run book action so that it no longer uses the "EM7 Central Database" credential. NOTE: After you update the PowerPack to version 103, ScienceLogic recommends that you edit the "Dell EMC: Unity Classify Root Device Class" run book action to change the Snippet Credential field to None. Please refer to the Dell EMC: Unity v103 Py3 PowerPack File Details in the PowerPacks section of the Support Portal for all information pertaining to the Dell EMC: Unity v103 Py3 PowerPack Support Status, Minimum SL1 Version, Solution Information, and Pricing Information. The Dell EMC: Unity v103 Py3 PowerPack Release File Details also contains links to the Release Notes, Manual, and PowerPack Info Report. Issues Addressed in the Dell EMC: Unity v103 Py3 PowerPack Release can be found in the Release Notes6Views0likes0CommentsNexus Community Scheduled Maintenance- Today Tues 11am PST
Hello Nexus Community Members, We have a scheduled maintenance window today (in about 30 minutes) at: 11 am PST 1 pm CST 2pm EST We do not anticipate any disruption to community access but always want to give you a heads up. As a best practice please save any content you are working on prior to that time. Please let us know if you have any questions or feedback. Best Regards, Nexus Community Team2Views0likes1CommentWeek 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.PavaniKatkuri5 days agoPlace Latest KB Articles and Known Issues BlogLatest KB Articles and Known Issues BlogModerator17Views0likes0CommentsFilter out VMware Virtual Machines from being monitored in SL1
We have approximately 300 virtual desktop VMware Virtual Machines that we do not want to monitor via the VMware Vcenter PowerPack in SL1. All other Virtual Machines and Virtual Hosts will be monitored as normal. Is there anyway of filtering/suppressing/vanishing these devices so we do not monitor them and they do not get counted in our licence count ?Solved28Views1like3CommentsEvent Suppression for CPU Util overnight
We have a server/device that has expected high CPU utilisation overnight, is there a way in SL1 for us to suppress this CPU Utilisation event on this server/device for a few hours during the night when high CPU utilisation is expected ? We want it to have the standard threshold for all other times of the day.Solved30Views0likes2CommentsSL1 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.pdf16Views1like0CommentsNexus 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 Team8Views0likes0Comments