You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Where there aren't MIBs to associate VLAN interfaces with actual VLAN IDs, NAV parses the interface name to "guess" the correct VLAN.
Only a few patterns are supported, typically something like VLAN(\d+)
For Juniper, NAV supports interfaces named irb for regular routers, but Juniper's firewall devices sport something called reth interfaces, whose name patterns are different, but can still be used to extract a VLAN number:
A fw device may have multiple reth interfaces, e.g. reth0, reth1 etc. The sub-interfaces with VLAN numbers in their name would be named reth0.100 for vlan 100, or reth1.100 for vlan 100 on on the reth1 interfaces. Upstream team says that the matching pattern is more like reth(\d+)\.(\d+), where the latter subpattern is the VLAN tag.
NAV patterns should be updated.
The text was updated successfully, but these errors were encountered:
Where there aren't MIBs to associate VLAN interfaces with actual VLAN IDs, NAV parses the interface name to "guess" the correct VLAN.
Only a few patterns are supported, typically something like
VLAN(\d+)
For Juniper, NAV supports interfaces named
irb
for regular routers, but Juniper's firewall devices sport something calledreth
interfaces, whose name patterns are different, but can still be used to extract a VLAN number:A fw device may have multiple
reth
interfaces, e.g.reth0
,reth1
etc. The sub-interfaces with VLAN numbers in their name would be namedreth0.100
for vlan 100, orreth1.100
for vlan 100 on on thereth1
interfaces. Upstream team says that the matching pattern is more likereth(\d+)\.(\d+)
, where the latter subpattern is the VLAN tag.NAV patterns should be updated.
The text was updated successfully, but these errors were encountered: