UM:Zones - Revision history

AlexKirhenshtein: Text replacement - "^" to "{{deprecated}}"

2022-09-13T16:14:00Z

Text replacement - "^" to "{{deprecated}}"

← Older revision		Revision as of 16:14, 13 September 2022
Line 1:		Line 1:
	Information moved to documentation:		{{deprecated}}Information moved to documentation:

	https://www.netxms.org/documentation/adminguide/advanced.html#zones		https://www.netxms.org/documentation/adminguide/advanced.html#zones

TatjanaDubrovica: Replaced content with "Information moved to documentation: https://www.netxms.org/documentation/adminguide/advanced.html#zones"

2017-11-24T14:10:05Z

Replaced content with "Information moved to documentation: https://www.netxms.org/documentation/adminguide/advanced.html#zones"

← Older revision		Revision as of 14:10, 24 November 2017
Line 1:		Line 1:
	~~{{DISPLAYTITLE~~:~~Zones}}~~		Information moved to documentation:
	As NetXMS server keeps track of an IP topology, it is important to maintain the configuration in which IP addresses do not overlap and that two IP addresses from same subnet are really within one subnet. Sometimes, however, it is needed to monitor multiple sites with overlapping IP address ranges. To correctly handle such situation, zoning must be used. Zone in NetXMS is a group of IP subnets which form non-overlapping IP address space. There is always zone 0 which contains subnets directly reachable by management server. For all other zones server assumes that subnets within that zones are not reachable directly, and proxy must be used.

	~~= Enable Zoning =~~		https://www.netxms.org/documentation/adminguide/advanced.html#zones

	Zoning support is off by default. To turn it on you must set server's configuration variable '''EnableZoning''' to 1 and restart server. After restart, server will create default zone with ID 0 and put all existing subnets into that zone. Subnet tree will looks like this:

	~~[[File~~:~~zoning_enabled~~.~~png]]~~


	~~= Setting communication options for zones =~~

	~~Server have to know proxy nodes to be able to communicate with nodes in remote zones~~. ~~Default proxy settings for all nodes in the zone can be set on '''Communications''' page in zone object properties:~~

	~~[[File:zone_comm_settings~~.~~png]]~~

	~~On this page you can set default proxy node for NetXMS agents, SNMP, and ICMP. Note that proxy node must be in default zone and must have primary IP reachable by NetXMS server.~~


	~~= Moving nodes between~~ zones =

	To move existing node to another zone, select '''Change zone...''' from nodes context menu, then select target zone in zone selection dialog that will appear. After move to another zone, server will immediately do configuration poll on the node.

Macro: minor wording corrections

2013-01-13T17:02:29Z

minor wording corrections

← Older revision		Revision as of 17:02, 13 January 2013
Line 1:		Line 1:
	{{DISPLAYTITLE:Zones}}		{{DISPLAYTITLE:Zones}}
	As NetXMS server keeps track of IP topology, it is important ~~that~~ IP addresses do not overlap and that two IP addresses from same subnet are really within one subnet. Sometimes, however, it is needed to monitor multiple sites with overlapping IP address ranges. To correctly handle such situation, zoning must be used. Zone in NetXMS is a group of IP subnets which form non-overlapping IP address space. There is always zone 0 which contains subnets directly reachable by management server. For all other zones server assumes that subnets within that zones are not reachable directly, and proxy ~~should~~ be used.		As NetXMS server keeps track of an IP topology, it is important to maintain the configuration in which IP addresses do not overlap and that two IP addresses from same subnet are really within one subnet. Sometimes, however, it is needed to monitor multiple sites with overlapping IP address ranges. To correctly handle such situation, zoning must be used. Zone in NetXMS is a group of IP subnets which form non-overlapping IP address space. There is always zone 0 which contains subnets directly reachable by management server. For all other zones server assumes that subnets within that zones are not reachable directly, and proxy must be used.

	= Enable Zoning =		= Enable Zoning =

217.22.89.98 at 09:40, 20 November 2012

2012-11-20T09:40:45Z

← Older revision		Revision as of 09:40, 20 November 2012
Line 1:		Line 1:
	{{DISPLAYTITLE:Zones}}		{{DISPLAYTITLE:Zones}}
	As NetXMS server keeps track of IP topology, it is important that IP addresses do not overlap and that two IP addresses from same subnet are really within one subnet. Sometimes, however, it is needed to monitor multiple sites with overlapping IP address ranges. To correctly handle such situation, zoning must be used. Zone in NetXMS is a group of IP subnets which form non-overlapping IP address space. There ~~are~~ always zone 0 which contains subnets directly reachable by management server. For all other zones server assumes that subnets within that zones are not reachable directly, and proxy should be used.		As NetXMS server keeps track of IP topology, it is important that IP addresses do not overlap and that two IP addresses from same subnet are really within one subnet. Sometimes, however, it is needed to monitor multiple sites with overlapping IP address ranges. To correctly handle such situation, zoning must be used. Zone in NetXMS is a group of IP subnets which form non-overlapping IP address space. There is always zone 0 which contains subnets directly reachable by management server. For all other zones server assumes that subnets within that zones are not reachable directly, and proxy should be used.

	= Enable Zoning =		= Enable Zoning =

Victor at 22:22, 3 November 2012

2012-11-03T22:22:14Z

← Older revision		Revision as of 22:22, 3 November 2012
Line 5:		Line 5:

	Zoning support is off by default. To turn it on you must set server's configuration variable '''EnableZoning''' to 1 and restart server. After restart, server will create default zone with ID 0 and put all existing subnets into that zone. Subnet tree will looks like this:		Zoning support is off by default. To turn it on you must set server's configuration variable '''EnableZoning''' to 1 and restart server. After restart, server will create default zone with ID 0 and put all existing subnets into that zone. Subnet tree will looks like this:

			[[File:zoning_enabled.png]]


Line 11:		Line 13:
	Server have to know proxy nodes to be able to communicate with nodes in remote zones. Default proxy settings for all nodes in the zone can be set on '''Communications''' page in zone object properties:		Server have to know proxy nodes to be able to communicate with nodes in remote zones. Default proxy settings for all nodes in the zone can be set on '''Communications''' page in zone object properties:

			[[File:zone_comm_settings.png]]

	On this page you can set default proxy node for NetXMS agents, SNMP, and ICMP. Note that proxy node must be in default zone and must have primary IP reachable by NetXMS server.		On this page you can set default proxy node for NetXMS agents, SNMP, and ICMP. Note that proxy node must be in default zone and must have primary IP reachable by NetXMS server.

Victor: Created page with "{{DISPLAYTITLE:Zones}} As NetXMS server keeps track of IP topology, it is important that IP addresses do not overlap and that two IP addresses from same subnet are really with..."

2012-11-03T22:19:07Z

Created page with "{{DISPLAYTITLE:Zones}} As NetXMS server keeps track of IP topology, it is important that IP addresses do not overlap and that two IP addresses from same subnet are really with..."

New page

{{DISPLAYTITLE:Zones}}
As NetXMS server keeps track of IP topology, it is important that IP addresses do not overlap and that two IP addresses from same subnet are really within one subnet. Sometimes, however, it is needed to monitor multiple sites with overlapping IP address ranges. To correctly handle such situation, zoning must be used. Zone in NetXMS is a group of IP subnets which form non-overlapping IP address space. There are always zone 0 which contains subnets directly reachable by management server. For all other zones server assumes that subnets within that zones are not reachable directly, and proxy should be used.

= Enable Zoning =

Zoning support is off by default. To turn it on you must set server's configuration variable '''EnableZoning''' to 1 and restart server. After restart, server will create default zone with ID 0 and put all existing subnets into that zone. Subnet tree will looks like this:

= Setting communication options for zones =

Server have to know proxy nodes to be able to communicate with nodes in remote zones. Default proxy settings for all nodes in the zone can be set on '''Communications''' page in zone object properties:

On this page you can set default proxy node for NetXMS agents, SNMP, and ICMP. Note that proxy node must be in default zone and must have primary IP reachable by NetXMS server.

= Moving nodes between zones =

To move existing node to another zone, select '''Change zone...''' from nodes context menu, then select target zone in zone selection dialog that will appear. After move to another zone, server will immediately do configuration poll on the node.