Jump to content

Duvak

Members
  • Content Count

    58
  • Joined

  • Last visited

  • Days Won

    2

Duvak last won the day on August 21 2019

Duvak had the most liked content!

Community Reputation

3 Neutral

My Information

  • Agent Count
    200+

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Hi All, A new day, a new challenge. I'm monitoring WatchGuard Firewalls now! It's great. I added a detection template, search and group so now I have all my WatchGuard Firewalls together in a group. So I build monitors on this group. SNMP monitors to check free mem, cpu and much more. So when my firewall has any performance problems, I can see it. Yeey! But there's one problem.... I cant enable data collection on group monitors for network devices 😞 So now nice graph, no historical data.... The data Collector fields are greyed out. I asked Support but they answered it's by design. But hey... I can override an individual monitor and enable Data Collection. So it sould be possible... He also answered it might be possible by modifying the agents in the database. He was not supposed to tell how so now I rely on you guys... 1. Who knows a way to enable data collection on these monitors like in the screenshot? 2. If via database... how do I make sure data collection will be enabled on any future added monitors when a WatchGuard Firewall is added? Hope someone will be able to tell me.
  2. Hi Martyn, Lets proove @kspooner is not right. I'm convinced the probe can do beautifull things and works well. This is not something the probe can't do but something that is poor design by HPe. Please reach out to me to see if we can make this work. I can make time for it. Unfortunate I don't see how slack works. I hit the Slack tab on top of this page. Enter my name and mail and check the cw-automate channel and agree. But right after clicking Join now it tells me ERROR!!! channel_not_found
  3. Ok, call me the stupidest man on earth but please tell me HOW i can reach you on Slack?
  4. Ok, call me the stupidest man on earth but please tell me HOW i can reach you on Slack?
  5. ooohh.. cr*p. Slack... not familliar with that. Let me try to figure that out first
  6. Hi All, Got a Challenge for some experienced engineers. Lets take a deep dive in the SNMP Collection tables in the Custom Table Walk. I'm trying to collect info from iLO devices to gather disk info. I found the disk info is related to OID table 1.3.6.1.4.1.232.3.2.5.1. So great! I can walk it and find the information I need. But now I discovered that the disk CONTROLLER can have an index on his own. So walking this oid results on one iLO this: But performing a walk on another iLO results in this: To safe you from searching: The part after 1.3.6.1.4.1.232.3.2.5.1.1 refers to the controller index (top 4, bottom 2) and AFTER the controller index, I get the disk indexes. So using this collection template doesn't show any good result: I was hoping this would work: but it does not accept this format as an integer. So the big question: How do I get there to get the right information? Anyone out there with a great idea!?
  7. Hi RIM, Using this one a year now without problems: Create a role detection. (attached that for you). I guess you know how to make a search and group for the result of the role detection? Enable the internal monitor (attached) to the group. This monitor checks once a day if EventID4 has been logged (successfull backup). Because it's a reversy query, it alerts when it's not been logged. Taking in count that the backup is running once a day.... Windows Backup Role.sql Windows Backup monitor.sql
  8. Hi jhubert, No sorry, but my experiance with upgrading from W7 to W10 is that the Automate Agents needs to be reinstalled. So starting the upgrade is no problem but getting it back in automate is a challenge.
  9. No you mention it.... I see. Thats strange. I would understand this when using a shared iLO port. But i'm using dedicated ones... Hope DEV will find something.
  10. But this finding will never be solved by ConnectWise... It's the iLO5 thats reporting the wrong information. So it should be logged with HPe. However, I logged a case with HPe but they never looked into this because i'm not using a approved tool. Asking what the approved tool should be, they never answered...
  11. Finaly... I found at least the ilo5 detection problem origin... In my case, the iLO5 was in another VLAN. So it will not be available in the ARP table from the probe. This rules out the ARP scan/detection. But for some reason, the iLO5 device will never respond the IP address from the iLO when checking OID 1.3.6.1.2.1.4.20.1.2.X but the IP address from the Server itself. So for example: The ilo is configured on 192.168.1.10 and the host has IP 172.17.10.33, the SNMP walk on this oid will show 172.17.10.33. This makes labtech not able to detect using SNMP rules because it does not match the IP address from the Ping Sweep. In other words: The probe will never detect iLO5 when in another VLAN. So next question: what can do about this.... I keep searching.
  12. Hi Steve I know it should work but it doesnt. Location deployment setting is set and domain admin account assigned in the probe setting. Never been able to push with success untill I run the agent service with admin account. Never logged a case for this since there is a simple workaround.
  13. Hi JosefNT, Have you tried to change the probe to run as local account instead of system account? I've never deployed an agent using the probe succesfull without turning this one on first. And you know... it sounds logic. The local System account on a probe does never have access to network resources. (or you need to use Run As) So once the probe's agent is running as domain admin, it should be able to access every domain computer on the network and deploy the agent. So enable the "guy in the box" icon and try again.
  14. Difficult topic.... I've added the routing firewall now to the scan subnets. Still no result. Frustrating part is that i can SEE all traffic passing by in the firewall. It scans all IP's and even the IP from the iLO5 device. First ping, then SNMP and after all a port scan to check available ports. So you should expect the device in the list but it does not appear. So i've got two questions: 1. It came to my attention the "Found Devices" tab in the probe's Network Devices remains empty. (same at every probe) is this expected? 2. So my situation has at least 3 vlans, connected with a routing firewall. The probe in VLAN "12" is scanning VLAN 11,12 and 14. It is able to find devices in all VLAN's. All except the iLO5 and the WatchGuard Firewalls. The firewall traffic logs show me valid traffic and is allowing all ports. Tried with both "Enable MAC Address Scanning" on and off. What can possibly be wrong? I still guess it's because the SNMP scan index being found as 127.0.0.1 and because of the clear explanation from Darren, SNMP scan seems to be the only solution for this setup. UPDATE: It all seems to be a problem with the devices. After taking a closer look, I found the problem. Now... I need the solution but it's not to solve by Automate. A walk on the iLO5 device shows 2 values when running a walk on 1.3.6.1.2.1.4.20.1.2. the first was 127.0.0.1 and the second was 172.30.30.10. strange part: the IP adres I walk on is 172.30.20.10. So it's a fault by the iLO snmp stack. Same is for the watchguard clsutered firewall with LAG, BOVPN and Vlans. Walking 1.3.6.1.2.1.4.20.1.2 result in a lot of IP addresses from all interfaces, except the management interface because it's a Virtual IP address. Strangest part is that WatchGuard support tells me this is by design. The only solution is to put the probe in the same vlan/subnet as the VIP from the watchguard to be able to detect it. I'm still working with HPe for the iLO solution.
  15. Hi Darren, Thanks for taking the time to explain the principles of the probe system. This made me think a bit more out-of-the box. Yes, the situation is not only a different subnet, it's a different VLAN. So thats why ARP doesn't show the devices. So next is de SNMP scan. My probe is configured to not scan it's own gateway (which is the firewall) because the management IP for the firewall is in a different VLAN. So i've added the gateway IP to the probe settings. Now I have to wait and see if the probe will learn. I'll keep you updated.
×
×
  • Create New...