Skip to main content
Flexible Top Header

Why Integrity still not support VLAN Management

  • July 7, 2026
  • 5 replies
  • 69 views
pascal.raemy
Forum|alt.badge.img

Hello, 

I started in 2008 with Bluecat. I requested many times to get the ability to manage VLAN in BAM. 

I am now in a migration from Efficient IP and also Infoblox. Both competitors support VLAN management, but Integrity NOT. For me it is a big challenge to try to implement VLAN Management into BAM, using Device and User defined Links. but this is not a good solution, it is like a Workaround to avoid the customer using back a Excel Sheet.

Integrity integrates more and more with the network. 

WHY does Integrity still not support VLAN Management? 

Any comment is welcome to force Bluecat look at the feature for the next release.

Pascal

    5 replies

    S
    • struttob
    • Consistent Uptimer
    • July 29, 2026

    Hello there,

     

    As a network architect myself I’m curious to know what this vlan management feature is and how it would typically be used in daily operations.  I did find the couple of paragraphs on the competitor’s web site but it wasn’t very clear on what it is or what meaningful data or function it provides.

    Could you please elaborate?


    Thanks so much!

     

     

     

    pascal.raemy
    Forum|alt.badge.img
    • pascal.raemy
    • Author
    • Consistent Uptimer
    • July 31, 2026

    Hello, 

    As a network architect, i hope you already worked with network guys who manage networks. 

    Since years you associate a VLAN-ID to a networks. The same VLAN-ID can be use more that one tome, if only use locally. You also create VLAN Range for location, i.e vlan 100 to vlan 199 is for  US, 200-299 for EU, and so on…. VLAN are always associated to a network. 

    With the BAM today, most of customers have an excel sheet to manage VLAN, because in the BAM you don’t have a VLAN Management Menu, like for example Device or TAG.

    I am just migrating from Efficient IP, and it has a VLAN Management, where you can define VLAN Range, have a list of VLAN ID with the associated Network.

    In the Past, Bluecat said: We are not a network company. But today.. it is a network company. That way i hope to get an enhancement of the BAM to provide VLAN Management. 

    Hope this help

     

      S

      I totally agree, we have a lot our VLAN information in Netbox because Bluecat does not support dedicated VLAN-Management. This is a feature I would love to see in Bluecat.

      dwm
      • dwm
      • DNS Hostmaster
      • August 20, 2026

      My understanding is that Integrity supports the addition of arbitrary user-defined metadata to various record-types, such as network blocks.

      Does it make sense to configure an optional user-defined field to your network records labelled, “VLAN ID”?

       ~ ~ ~

      That said, things can get much more complicated with modern software-defined networks, where (for example) the same broadcast domain can be straightforwardly presented using arbitrary different VLAN IDs in different contexts.

      Building something sufficiently flexible and general purpose with the same richness of data model as, say, Netbox is quite a big ask.

      Now, if Bluecat came out and said they had a nice slick solution for keeping Netbox date up to date from information held in Integrity and/or vice-versa, that would be of particular interest to me.

      (Unix philosophy: do one job, do it well, and make it easy to compose / integrate with other tools. in a loosely-coupled way)

      pascal.raemy
      Forum|alt.badge.img
      • pascal.raemy
      • Author
      • Consistent Uptimer
      • August 20, 2026

      Thank for you comment. 

      Either using Customer Fields or customer Link are for me and customers Workaround. Customers would like to see a menu called VLAN where you manage VLAN, like creating VLAN Group.

      Then you can link the VLAN-ID to Networks. like we do with Device. 

      It should not be complicated to implement this.

      Terms & ConditionsAccessibility statement