The naming scheme for user-defined tagging is based on user-specified tags in user-created IP tag filters. The tagged naming examples included in this section are based on the following two IP tag filter groups:

  • Router-PE1 containing:

    • Matching criteria that allows only router PE 1 to become a member of the Router-PE1 group

    • User-specified tag = cust1

    • Overlapping IP address range = 10.1.0.2

    • Route distinguisher = enabled (default)

  • Router-PE2 containing:

    • Matching criteria that allows only router PE 2 to become a member of the Router-PE2 group

    • User-specified tag = cust2

    • Overlapping IP address range = 10.1.0.2

    • Route distinguisher = enabled (default)

      Note:

      The following discussion assumes DisableOverlappingIP = FALSE

      Tagged IP objects representing non-VRF IP overlapping addresses appear in the topology as:

      Name: IP-<IP address>/<user-specified tag>

      DisplayName: <user-specified tag>:<IP address> [<system containing this IP>]

      Corresponding tagged IPNetwork object:

      Name: IPNET-<IP network>/<user-specified tag>

      DisplayName: <user-specified tag>:<IP network>

      Tagged IP objects representing VRF IP addresses appear in the topology as:

      Name: IP-<IP address>/<user-specified tag>-<RD tag>

      DisplayName: <user-specified tag>-<RD tag>:<IP address> [<system containing this IP>]

      Examples:

      Name: IP-10.1.0.2/cust1-29

      DisplayName: cust1-29:10.1.0.2 [PE 1]

      Name: IP-10.1.0.2/cust2-107

      DisplayName: cust2-107:10.1.0.2 [PE 2]

      Corresponding tagged IPNetwork object:

      Name: IPNET-<IP network>/<user-specified tag>-<RD tag>

      DisplayName: <user-specified tag>-<RD tag>:<IP network>

      Examples:

      Name: IPNET-10.1.0.0/cust1-29

      DisplayName: cust1-29:10.1.0.0

      Name: IPNET-10.1.0.0/cust2-107

      DisplayName: cust2-107:10.1.0.0

      The preceding examples demonstrate the double-tagging capability. Because IP address 10.1.0.2 is a VRF IP and because the route distinguisher parameter is enabled in the Router-PE1 and Router-PE2 IP tag filter groups, the IP objects created for IP address 10.1.0.2 are double-tagged.

      By disabling the route distinguisher parameter in the filter groups and invoking a rediscovery of the topology, the IP objects for IP address 10.1.0.2 will receive a single tag:

      Name: IP-10.1.0.2/cust1

      DisplayName: cust1:10.1.0.2 [PE 1]

      Name: IP-10.1.0.2/cust2

      DisplayName: cust2:10.1.0.2 [PE 2]

      By disabling the route distinguisher parameter in just one of the groups, say Router-PE1, and performing a rediscovery of the topology, the IP objects for IP address 10.1.0.2 will be named as follows:

      Name: IP-10.1.0.2/cust1

      DisplayName: cust1:10.1.0.2 [PE 1]

      Name: IP-10.1.0.2/cust2-107

      DisplayName: cust2-107:10.1.0.2 [PE 2]