Zenoss ZenTech Community

Getting Zenoss to Initiate WinRM Traffic

Subject:	Getting Zenoss to Initiate WinRM Traffic
Author:	V Arnens
Posted:	2018-05-12 14:28

Greetings,

I am a novice Zenoss administrator but believe I have read through enough documentation to be able to at least formulate my question and the steps I have taken in response to the issue I'm facing.

I recently inherited two Zenoss 4.2.5 implementations that have been configured for mostly SNMP v2c monitoring across a varied infrastructure, and have been tasked with replacing the monitoring on the Windows side with WinRM in place of SNMP.

I've completely configured the WinRM infrastructure itself, including all server-side configs and firewall allowances. Outside of Zenoss, WinRM works as expected. On the Zenoss side, I modified the zProperties for WinRM in the class [Server > Microsoft > Windows] to reflect the right username, password, and KDC. While doing this, I also configured the zSnmpMonitorIgnore property to true in an attempt to migrate the monitoring entirely to WinRM.

With this setup in place (and the WinRM modeler plugins also available), I set out to discover a device which I know is accessible through WinRM. I ensure that I'm discovering it in the correct device class, and initiate the process. Here, the discovery process simply stalls at Looking for [Device]... (I've included a log excerpt below).

When I analyze network traffic on the next hop (I'm discovering a device on a different VLAN), I don't see Zenoss actually initiating any WinRM traffic to begin with. It's not the case that WinRM traffic from Zenoss is being filtered somewhere, it's just not being initiated to begin with.

I was wondering if someone could point me in the right direction as far as what particular logs to focus on here, or whether there is some check that I missed. It seems there is some component within Zenoss that is just not initiating the WinRM traffic to begin with during the discovery process.

[Excerpt]
2018-05-11 19:18:23,111 INFO zen.Job: Spawning subprocess: /opt/zenoss/bin/zendisc run --now -d [Device IP] --monitor localhost --deviceclass /Server/Microsoft/Windows --prod_state 1000 --job b94a90g1-c166-4c67-84f7-2cf252dce801
2018-05-11 19:18:37,722 INFO zen.ZenDisc: Connecting to localhost:8789
2018-05-11 19:18:37,730 INFO zen.ZenDisc: Connected to ZenHub
2018-05-11 19:18:37,945 INFO zen.ZenDisc: Looking for [Device IP]

------------------------------
V. Arnens
------------------------------

Subject:	RE: Getting Zenoss to Initiate WinRM Traffic
Author:	Jane Curry
Posted:	2018-05-16 09:56

Discovery will start by trying to do a ping of the device - will that work in your environment?

Not quite sure how you are trying to add your device? Try adding a sample device under /Server/Microsoft/Windows (Click the + icon at the top of the display that shows devices in the /Server/Microsoft/Windows device class. I have just done that and supplied 1.2.3.4 as the device to add and it worked fine. I would also tick the box so that it doesn't get modeled as part of the discovery. Modeling is where the WinRM stuff happens to discover characteristics and components of you r windows devices. Once you have the device added, then you can select it and use the Action icon (gear) at the bottom of the left-hand menu, to model the device.

Cheers,
jane

------------------------------
Jane Curry
Skills 1st United Kingdom
jane.curry@skills-1st.co.uk
------------------------------

Previous
Cisco IP SLA threhsolds

Next
Zenoss 4.2.5 job_catalog corrupted and POSKeyError