Creating an IP tag filter group

An IP tag filter group has two sets of matching criteria:

• System

  The membership class for an IP tag filter group is UnitaryComputerSystem. Only the discovered systems matching the matching criteria (attributes that are specified for UnitaryComputerSystem) for a particular group can become members of that group.

• IP address range

  The IP address range matching criteria consists of two IP address ranges: one for management IP addresses and one for overlapping IP addresses. Each of the ranges may contain a single IP address. Only the IP addresses collected for the discovered system matching either of the IP address ranges will be tagged in accordance to the user-specified tag for the group.

  If a system (device) matches the system criteria for the filter, all IP addresses collected for the discovered system are subject to the management IP address range and the overlapping IP address range defined for the filter. If a system does not match the system criteria for the filter, none of the IP addresses collected for that discovered system are subject to the two IP address ranges defined for the filter.

  If an IP address falls within the management IP address range, the user-specified tag for the filter is applied to the IP object created for that IP address. If the IP address does not fall within that range, the user-specified tag for the filter is not applied to the IP object created for that IP address:

• Any management IP object created for an IP address matching the management IP address range is MANAGED by default. You can change the value to UNMANAGED by selecting UNMANAGED from the MonitorMgmtIP drop-down menu.

• Any management IP address created for an IP address matching the management IP address range is excluded from the overlapping IP address range defined for the IP tag filter group.

  If an IP address falls within the overlapping IP address range, the user-specified tag for the filter is applied to the IP object created for that IP address. If the IP address does not fall within that range, the user-specified tag for the filter is not applied to the IP object created for that IP address:

• Any overlapping IP object created for an IP address matching the overlapping IP address range is UNMANAGED by default. You can change that value to MANAGED by selecting MANAGED from the MoinitorOverlappingIP drop-down menu.

  The RouteDistinguisher parameter (ENABLE_RD or DISABLE_RD; ENABLE_RD by default) for an IP tag filter group is applicable to all VRF IP addresses that fall within the overlapping IP address range defined for the filter. For an enabled RouteDistinguisher parameter, any IP address falling within the range of the overlapping IP address range is tagged with the route distinguisher name that is associated with the VRF to which that IP address belongs. (The IP Manager gathers route distinguisher information by reading the vendor VPN MIB on the discovered system.) Conversely, if the RouteDistinguisher parameter is disabled, any VRF IP address falling within the overlapping IP address range is not tagged with the route distinguisher value.

  Note:

  VRF IP addresses not falling within the overlapping IP address range will be tagged with the route distinguisher value regardless of the RouteDistinguisher parameter setting (ENABLE_RD, DISABLE_RD). The RouteDistinguisher parameter setting applies only to the VRF IP addresses that fall within the overlapping IP address range defined for the filter.

  Single tagging and double tagging of an IP object created for a discovered IP address are both possible. “IP tag naming scheme” on page 216 provides descriptions and examples of single- and double-tagged IP objects.