Tavve zoneranger User Manual page 40

Grouping
Grouping is another concept that applies when multiple ZoneRangers are deployed into the same
network partition. A set of ZoneRangers is considered to be grouped when they are all configured with
the same group name
features:
•
The Ranger Gateway's algorithm for de-duplicating forwarded SNMP traps and Syslog
messages depends on grouping, in that if a Ranger Gateway receives duplicate SNMP traps or
Syslog messages forwarded from multiple ZoneRangers, the duplicates will be removed only if
the configured group names of the forwarding ZoneRangers are identical.
•
When
community@ZoneRanger@device
conjunction with SNMP Get/Set proxy, if the group name is used in place of the ZoneRanger in
the community string, the Ranger Gateway will select one of the joined ZoneRangers in the
group to relay the request to the managed device.
Note that it is possible to configure a set of ZoneRangers to have the same group name with or without
configuring redundancy. For example, if a pool of ZoneRangers is configured without configuring
redundancy, the group names of each of the ZoneRangers in the pool still need to match in order for
SNMP trap and Syslog message de-duplication to work properly. If redundancy is configured, the
redundant ZoneRangers will automatically have the same group name (i.e. the group name from the
source ZoneRanger will be propagated to any target ZoneRangers).
6 The group name of a ZoneRanger can be configured during initial configuration, or at any subsequent
time via the ZoneRanger web interface.
ZoneRanger 5.5 User's Guide
6 . Grouping impacts the behavior of the Ranger Gateway with respect to two proxy
using one of the three-part community
or
device@ZoneRanger@community
string formats (i.e.
) in
40