Make Device heatbeat service to use TCP port instead of zenping

[XiangJun Wu]

XiangJun Wu [http://community.zenoss.org/people/goafter1981] created the discussion

"Make Device heatbeat service to use TCP port instead of zenping"

To view the discussion, visit: http://community.zenoss.org/message/71512#71512

--------------------------------------------------------------
Hello guys,

I find in some situation firewall may blocks icmp requests between zenoss and my device.
In default, ping is used as heart beat service by zenoss.
Can I change that for some kinds of device to use tcp port as heart beat service?

Thank you.
I want to know the steps.
--------------------------------------------------------------

Reply to this message by replying to this email -or- go to the discussion on Zenoss Community
[http://community.zenoss.org/message/71512#71512]

Start a new discussion in zenoss-users by email
[discussions-community-forums-zenoss--***@community.zenoss.org] -or- at Zenoss Community
[http://community.zenoss.org/choose-container!input.jspa?contentType=1&containerType=14&container=2003]

[Shane Scott]

Shane Scott [http://community.zenoss.org/people/hackman238] created the discussion

"Re: Make Device heatbeat service to use TCP port instead of zenping"

To view the discussion, visit: http://community.zenoss.org/message/71536#71536

--------------------------------------------------------------
Xiang:

For this you'll want to set the zPingIgnore to True. You can then setup a trigger for the http test and a notification command that uses zensendevent to create a ping down event for the device when the http test triggers an event. you can create a similar trigger and notification set for the clears.

You can also do this with transforms, but it would be a little complicated.

Best,
--Shane Scott (Hackman238)
--------------------------------------------------------------

Reply to this message by replying to this email -or- go to the discussion on Zenoss Community
[http://community.zenoss.org/message/71536#71536]

Start a new discussion in zenoss-users by email
[discussions-community-forums-zenoss--***@community.zenoss.org] -or- at Zenoss Community
[http://community.zenoss.org/choose-container!input.jspa?contentType=1&containerType=14&container=2003]

[XiangJun Wu]

XiangJun Wu [http://community.zenoss.org/people/goafter1981] created the discussion

"Re: Make Device heatbeat service to use TCP port instead of zenping"

To view the discussion, visit: http://community.zenoss.org/message/71523#71523

--------------------------------------------------------------
Scott,

Thank you for your reply.
We can get information from ipservice component. For windows, we want to monitor 3389 and for linux, we want to monitor 22.

Can we use existing ipservice to trigger such command or we must write check_port monitor via command?
--------------------------------------------------------------

Reply to this message by replying to this email -or- go to the discussion on Zenoss Community
[http://community.zenoss.org/message/71523#71523]

Start a new discussion in zenoss-users by email
[discussions-community-forums-zenoss--***@community.zenoss.org] -or- at Zenoss Community
[http://community.zenoss.org/choose-container!input.jspa?contentType=1&containerType=14&container=2003]

[Shane Scott]

Shane Scott [http://community.zenoss.org/people/hackman238] created the discussion

"Re: Make Device heatbeat service to use TCP port instead of zenping"

To view the discussion, visit: http://community.zenoss.org/message/71550#71550

--------------------------------------------------------------
XiangJun Wu:

You could use the ipservice test, but to be honest, the check_port command datasource will probably be much more reliable.

Best,
--Shane Scott (Hackman238)
--------------------------------------------------------------

Reply to this message by replying to this email -or- go to the discussion on Zenoss Community
[http://community.zenoss.org/message/71550#71550]

Start a new discussion in zenoss-users by email
[discussions-community-forums-zenoss--***@community.zenoss.org] -or- at Zenoss Community
[http://community.zenoss.org/choose-container!input.jspa?contentType=1&containerType=14&container=2003]