Open for Voting
over 2 years ago

Vlan management view in IPAM

We looked IPAM decision within two weeks and as you wrote below we can say you several feature request.

First of all is it possible to create vlan management tool where we can create vlans without networks? Because very often we create unroute vlans where IP addresses unrouted.

Second request is creating logical concept like «virtual domain» that is a group with set of unique vlans. For instance we have 3 locations -  Headquarted, DataCenter, BranchOffice with unique ip networks(except guests vlan, who had access to Internet only, over NAT) but the same set of vlans.

HQ:vlan333-management:10.1.1.0/24

HQ:vlan10-servers:10.10.1.0/24

HQ:vlan800-clients:10.100.1.0/24

HQ:vlan666-guests:192.168.1.0/24

DC:vlan333-management:10.1.2.0/24

DC:vlan10-servers:10.10.2.0/24

BO:vlan333-management:10.1.3.0/24

BO:vlan10-servers:10.10.3.0/24

BO:vlan800-clients:10.100.3.0/24

BO:vlan666-guests:192.168.1.0/24

This sort of situation happened very often.

Parents
  • We have the concept here of VLAN spaces; a router interface defines the VLAN space, so we can standardize the layer-2 configuration in a building.

    it's much easier not having to figure out what the management vlan is in a building when hanging a switch, because it's always the same...

Comment
  • We have the concept here of VLAN spaces; a router interface defines the VLAN space, so we can standardize the layer-2 configuration in a building.

    it's much easier not having to figure out what the management vlan is in a building when hanging a switch, because it's always the same...

Children
No Data