Trend Micro Network VirusWall™ Enforcer 2500 Administrator’s Guide
B
-
8
•
In one-way communication mode, the Control Manager agent periodically sends
out query commands to Control Manager. This periodical query behavior works
like a heartbeat and is treated as such by Control Manager.
The Control Manager agent heartbeats implement with the following ways:
•
UDP:
If the product can reach the server using UDP, this is the most lightweight,
fastest solution available. However, this does not work in NAT or firewall
environments. Also the transmitting client cannot make sure that the server does
indeed receive the request.
•
HTTP/HTTPS:
To work under a NAT or firewall environment, a heavyweight
HTTP connection can be used to transport the heartbeat
Control Manager supports both UDP and HTTP/HTTPS mechanisms to report
heartbeats. Control Manager server finds out which mode the Network VirusWall
Enforcer 2500 device applies during the registration process. A separate protocol
handshake occurs between both parties to determine the mode.
Aside from simply sending the heartbeat to indicate the product status, additional
data can upload to Control Manager along with the heartbeat. The data usually
contains Network VirusWall Enforcer 2500 device activity information to display on
the console.
Using the Schedule Bar
Use the schedule bar in the Communicator Scheduler screen to display and set
Communicator schedules. The bar has 24 slots, each representing the hours in a day.
Blue slots denote Working status or the hours that the Communicator sends
information to the Control Manager server. White slots indicate Idle time. Define
Working or Idle hours by toggling specific slots.
You can specify at most three consecutive periods of inactivity. The sample schedule
bar below shows only two inactive hours:
The active periods specified by the bar are from 0:00 A.M. to 7:00 A.M, 8:00 A.M to
3:00 PM, and from 6:00 P.M. to 12:00 P.M.
