But it does not contain the VLAN Interface ID, which in this case would be 44. My proposal would be to add the ID as vlaninterfaceid, similar to the already included virtualinterfaceid:
Maybe this could be a one-liner in SwitchConfigurationGenerator.php, but I really don't know any remotly modern PHP, so I'm not entirely sure.
Why?
The VLAN interface ID is already used outside IXP Manager, most prominently for sflow things and Bird configuration, where the protocol names look something like pb_0044_as553. The 0044 is an expanded VLAN interface ID.
I would like to make monitoring and alerting to be aware of which sessions belong to which interfaces. With that, we can have a dashboard that shows all the information that belongs to an interface, including the BGP sessions running on it. Or we could have smarter alerting that won't bug you with BGP session alerts while the port is down.
Alternatives
Well, the vliid in the Bird protocol/filter names could be replaced by something else (?) but I think it's a quite clever solution.
A workaround would be to write a script that fetches layer2interfaces and sflow-db-mapper/configured-macs (bear with me), because that includes something like "0896ad260cc9":44 and use that to map the MAC in layer2interfaces to the MAC in configured-macs and get the vliid, but that's far from bullet proof and quite a hack...
Feature
The output of the
layer2interfacesAPI endpoint returns something like this:But it does not contain the VLAN Interface ID, which in this case would be
44. My proposal would be to add the ID asvlaninterfaceid, similar to the already includedvirtualinterfaceid:Maybe this could be a one-liner in
SwitchConfigurationGenerator.php, but I really don't know any remotly modern PHP, so I'm not entirely sure.Why?
The VLAN interface ID is already used outside IXP Manager, most prominently for sflow things and Bird configuration, where the protocol names look something like
pb_0044_as553. The0044is an expanded VLAN interface ID.I would like to make monitoring and alerting to be aware of which sessions belong to which interfaces. With that, we can have a dashboard that shows all the information that belongs to an interface, including the BGP sessions running on it. Or we could have smarter alerting that won't bug you with BGP session alerts while the port is down.
Alternatives
Well, the
vliidin the Bird protocol/filter names could be replaced by something else (?) but I think it's a quite clever solution.A workaround would be to write a script that fetches
layer2interfacesandsflow-db-mapper/configured-macs(bear with me), because that includes something like"0896ad260cc9":44and use that to map the MAC inlayer2interfacesto the MAC inconfigured-macsand get thevliid, but that's far from bullet proof and quite a hack...