Uploaded image for project: 'Network Observability'
  1. Network Observability
  2. NETOBSERV-2083

Make network name scope enabled for 2dary interfaces

    • Icon: Story Story
    • Resolution: Unresolved
    • Icon: Undefined Undefined
    • None
    • None
    • FLP
    • 3
    • False
    • None
    • False

      As mentioned here NETOBSERV-2082, network names fields are populated when using UDN, and when using secondary interfaces.

      In both cases they are visible as columns and filters, but only with UDN they are also a topology scope.

      We could also enable them without UDN, when secondary interfaces (indexes) are configured in FLP. We could do that simply in the operator, by creating a new frontend feature (e.g "networkNames") and make it enabled either if UDN is enabled, or if FLP is configured with 2dary interfaces.

       

      Also (perhaps a different task): an optimization can be done in FLP, to not populate "Primary" network name when neither UDN nor 2dary interfaces are configured.

              Unassigned Unassigned
              jtakvori Joel Takvorian
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated: