Create VLAN Custom Setting

Content Authoring
1

I am trying to find the best way to create a custom setting labeled ‘VLAN_ID’ and populate that based on the subnet location. I was testing this out with the Location Property Wizard, but I am not having much luck. Any thoughts or ideas?

2

Is the end goal to have the Subnet in a client setting for comparison?

3

We use the cidr string as a subnet identifier.

See https://developer.bigfix.com/relevance/reference/network-adapter.html#cidr-string-of-network-adapter-string

Keep in mind that “VLAN” does not equal “subnet” where networking is concerned; I haven’t found a way to pull VLAN information from an endpoint, as this is more of a network type information than endpoint data. CIDR is entirely possible, and useful, however. We consistently find endpoints that are not configured correctly by comparing CIDR data from the endpoint to IP data from our IP management tools.

1 Like
4

I am going to base my VLAN information via subnet CIDR. I am using this relevance ((cidr string of it) of adapters of network) to gather the CIDR and then I am trying to create a task that will update the custom setting to a VLAN location.

1 Like
5

Just out of curiosity, why the need for a client setting that contains this information? Any action or inspection you do with BigFix that I can think of could just use the inspection directly instead of relying on a client setting.

At least in our environment, network information is highly dynamic, so the client setting could be outdated as soon as the machines networking information changes, be that restart, undock, VPN connection established, and so on.

6

I am mainly wanting this for servers where the VLAN will never change. I am trying to gather this information to automate some populate into our CMDB since we are mostly using our BigFix analyses that I have been creating for this. We are not worried as much as location for workstations, but servers are my main focus right now.

7

Right, but why a client setting instead of a property? It just seems a little backwards to use an action to put information into a client setting that is then read somehow, when that information could simply be stored in a property without the need for a client action.

While I get that servers may change networking information less frequently than workstations, I would personally never say never :slight_smile:

2 Likes