Uploaded image for project: 'vpp'
  1. vpp
  2. VPP-667

Bridge Domains should have an API call to update MAC-age

XMLWordPrintable

    • Icon: Improvement Improvement
    • Resolution: Done
    • Icon: Low Low
    • None
    • None
    • L2

      John (Lo),

      So, I see that, when creating a bridge domain using the API
      call bridge_domain_add_del, one can specify some feature
      flags of the domain as well as the mac-age parameter.

      Later, it looks like one can alter the feature flags using the
      API call bridge_flags, changing one or more features to be
      enabled or disabled on the fly.

      However, it looks like there is no mechanism to alter just
      the mac-age parameter.

      So, a few questions. Is one expected to re-issue the bridge
      domain "add" request again, with all the same flag-bits, but
      with the new mac-age value? Or is this just a missing API
      call that is yet to be added?

      In particular, I notice that the code in src/vnet/l2/l2_bd.c has a
      command to set a new mac-age, but it doesn't make an API
      call to do so; instead it appears to go directly to the underlying
      implementation to affect a change.

      Any advice here?

      Thanks,
      jdl

      Hi Jon,

      Yes, you are right. There is no API to change the aging interval of a BD. It seems when MAC aging support was added to VPP, a new CLI but no API was added to change the aging value of a BD. It should be fairly straightforward to add this new API except we are now in API freeze for 17.04 release. Without a new API, I suppose the only way to change MAC aging in a BD is to use the bridge_domain_add_del API to specify all the feature flags and MAC aging value to overwrite the current BD setting.

      Regards,
      John

            lojohn John Lo
            jdl Jon Loeliger
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved:

                Estimated:
                Original Estimate - 2 days
                2d
                Remaining:
                Remaining Estimate - 2 days
                2d
                Logged:
                Time Spent - Not Specified
                Not Specified