Jump to content

Search the Community

Showing results for tags 'hp'.

More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • MSPGeek
    • The Geek Cast
    • Code of Conduct
  • ConnectWise Automate / Labtech
    • ConnectWise Automate / LabTech
    • ConnectWise Automate / LabTech - Development


  • ConnectWise Automate
    • Scripts
    • Plugins
    • SQL Snippets
    • Role Definitions
    • Automate PowerShell Code
    • Reports
    • Internal Monitors
    • Remote Monitors
  • ConnectWise Manage
    • API Interacting Code

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...


  • Start



About Me


Agent Count













Found 6 results

  1. Version 1.0.0


    This bundle will create the following Role: HP Server And the following sub-roles: HP Server - Gen6 HP Server - Gen7 HP Server - Gen8 HP Server - Gen9 HP Server - Gen10 I don't do a lot with HP servers, so these roles are not heavily tested. If you see anything detected incorrectly, please let me know so that I can update the role detection definition. To import these Role Definitions, in the ConnectWise Automate main screen, go to Tools > Import -> SQL File. Browse to the relevant file, and OK the message about inserting 6 rows.
  2. Standard Disclaimer Applies This is an attempt to document how I am monitoring SNMP for Proliant servers through Labtech. It is a merger of the previous 2 threads on the subject along with my notes from setting it up and muddling through SNMP after years of not looking at it at all. Forgive anything I put in wrong, and please comment it so I can change the content and wording to be as exact as possible. NOTE: This is not my whole solution, but should be enough for anyone to build out their own. Once I figured it out I created all the monitors I wanted ;). Process: Make sure the SNMP feature is installed Configure the SNMP service Make sure all the boxes are checked and set the contact and location information -- THIS STEP MUST BE COMPLETED MANUALLY ON EACH MACHINE Set up your community strings (one has to be read/write for insight, mine autocreated; one read only, for testing purposes I just used public,admin,proliant for my test values, change for production) Set it up to accept from the local host Install The Insight Management Agents and WBEM providers from HP and their prerequisites Go to the HP support site: https://support.hpe.com/hpesc/public/home Type in the box a recent server (DL380 gen9 or so) Click drivers & download Select OS ilo 3/4 Channel driver for server 2016 webpage (prereq) iLO 3/4 Management Controller Driver Package for Windows Server 2016 webpage (prereq) HP Insight management Agent x64 download webpage HPE Insight Management WBEM Providers for Windows Server x64 webpage My preferred method for this is to setup the standard build for the server (OS and features wise) with SNMP enabled and configured and then run the SPP on the machine and upgrade everything, etc. Create a group to add your remote monitors to. Add a known proliant server to the group for testing, preferably one you have quick physical access to. Start the SNMP service, and all the insight management agents listed as dependencies on the SNMP service. Add the MIB files from the HP SIM MIB kit. I found this website to be more helpful than manually trying to read through those MIB files (The link is to the MIB tree that contains the drive array status). Find 'condition'. For now I am only using Scalar Integers with fast and easy go/no-go criteria. Update: My Manual Run script pulls the end OIDS from a table and creates a monitor for each of them, food for thought. The Only ones I actually had to add for this were CPQHOST-MIB, CPQIDA-MIB, CPQHLTH-MIB if I remember correctly. But why not have those OIDS for when your probe walks and to use for detection templates!! See this thread on how to fix up those MIBS so they don't get pesky on import. Labtech's guidance on loading up those pesky MIB files. Add remote monitors against your group(s) on what you'd like to monitor. I added one for the SNMP Service against my mid level SNMP/Windows group. In addition to the following on the HP Proliant sub-group: I did the alert continuous alert style and made the subject something like "%name% %state% on %computername%" or "Proliant SNMP Monitoring Dependency failed" for success and failure. I then input in the failure/success messages what the return conditions mean to aid in troubleshooting. Remote monitors for these services at a minimum: CpMgHost, CpqNicMgmt,CqMgServ, CqMgStor (Name Convention: SVC - %servicename% (SNMP)) Remote Monitors for each OID you want to monitor (Name Convention: SNMP - HP Proliant - Drive Array) Test your monitors (pull a drive to degrade the array! unplug a power supply! hit a drive with a hammer before installing it! perform other testing actions!) One you have verified this is working on your test server, then I would import the XML scripts in the following order: EDFS in any order Scripts - I set this up so you have 3 groups (SNMP>Windows>HP) on the windows group you schedule run the scripts that install SNMP and configures it daily, and autojoin using search for EDF 'Use SNMP' and server OS, windows (not in my included scripts). Then on the HP Group the magic happens; there is the master script that first checks to make sure SNMP is marked as installed, then enabled, then installs all the software in order using the latest download links I could find. If it is already configured the script exits with no ticket. If windows can't get SNMP, you get the 'general failure' ticket. If any software fails, you get 2 tickets; one for the offending software, and the general one. So with only 3 scripts scheduled, it installs SNMP, configures it, and then installs all the prerequisites for SNMP monitoring on these devices. You have to setup your own ticket comments and finishes. For the application install scripts make sure they are all 'Isolated' and are using the latest EXEs (they get updated about every quarter or two). I used the following community strings on my test machine, search for references to them and change them to your production key like I did!: public,admin,insight,proliant You have to go into the Manual Run-% script to setup your community key in the SQLINSERT statement. This script creates remote monitors for each physical drive as reported by SNMP. Remote Monitors -- I will export some of the remote monitors I make. They are setup currently to monitor: Drive Arrays, Temperature System, CPU Fans, ASR, Resilient Memory, System Fans, and a few others. Recommend importing against a known proliant machine computerid (yes you have to modify each file, I set the computerid in the export to %computerid% on all files by opening them all in notepadplusplus then doing a replaced against my computeridfield )then drag to your groups. Add the searchs to the groups to add the rest of your servers. UPDATES: Added in hyperlink to Darren's MIB import fix batch file Changed wording to be more exact Added in what services I find it necessary to monitor added links Added a verbose roadmap added some scripts, edfs, searches, etc that I am using. Credits: Myself @DarrenWhite99 : Link inside on MIBs and help making the other things @Joe.McCall : https://www.labtechgeek.com/topic/2827-hp-server-hardware-monitoring/ @HickBoy : https://www.labtechgeek.com/topic/3756-hp-smartarray-monitoring/?do=findComment&comment=22997 SNMP HP Proliant.zip Remote Monitors.zip Physical Drive Ticketing (export).xml
  3. I am trying to query wmi for HP Server health but I cannot figure out how to do this with an alternate namespace. Does anyone know how to do this? I can do it with powershell but I am getting strange results.
  4. Hello. I've been using labtech for about 2 years but never had to dig super deep down into custom settings so forgive my ignorance. Our client noticed a failed drive on his HP Proliant DL380 Gen8. Labtech is showing no alerts or issues with the server. I see in the windows system event logs, entries for the failed drive array (see attached). I called Connectwise support and they said they don't know why we didn't get an alert and our server must have have smart monitoring enabled in the BIOS. I told them if I open an SMART checking application it can see the drives from the OS and reports SMART infomation. They replayed just saying they don't monitor HP smart arrays and I need to make a custom rule. Since we have over 2500 agents and a lot of HP Proliant servers, I became concerned. Is this accurate? do I need to make custom alerts to monitor all HP RAID events? Thanks for any guidance you can provide.
  5. New to Labtech and I'm trying to wrap my head around monitoring network devices. I am curious to know what the add-ons under the Network Device Solution section of the Solution Center actually do Firewall Devices, Network Devices (Complete Set), Wireless Devices, etc. I have installed them but can't seem to find any reference to them in Automate anywhere and there isn't any real information as to what they are or what they are used for. I appreciate any advice you can provide. Thanks!
  6. This is a set of scripts I built out to automate configuration of SNMP monitoring of core hardware components on our HP servers. It uses a couple of EDF's to track whether SNMP is installed and configured. I also included a search for filtering down to just your physical HP servers so it's not trying to install on vMware vm's or the like. Implementation requirements: - Server must have SNMP installed - Server must have HP(E) Insight Management Agent installed - SNMP must be configured to allow queries I have included the scripts I built to accomplish each of these steps, a master script that I use to check and complete each step as needed (the script steps to run each subscript were removed so it would export at a reasonable size, so some minor edits are required) as well as a txt file with the OID's and check results I use in the SNMP remote monitors. Enjoy! Contribute! Automate! HP Server SNMP Monitoring.zip
  • Create New...