Users Guide

Working with VLAN Domains | VLAN Visualization
676 OMNM 6.5.3 User Guide
To illustrate this, let us consider the following example. Assume you have two devices, "Device1",
and "Device2". On both of them, VLANS 10, 20, and 30 exist. If you had run the "Get VLAN
Data" action against Device1 and Device2, and ports/interfaces on Device1 and Device2 were
tagged/untagged in those VLANs, you would find the following:
• VLANs 10, 20, and 30 would exist , and entries for them would be visible in the "VLANs"
portlet.
• As there were no VLAN Domain Assignments for anything on either device, each of those
VLANs would be assumed to exist on the Default VLAN Domain. Thus, in the "VLANs"
portlet, you would see entries for VLAN10, VLAN20, and VLAN30, and each of them would
be "assigned" to the "Default" VLAN Domain.
• In the "VLAN Memberships" portlet, you would find membership entries for all VLAN ports/
interfaces, on either device, and they would all be associated with the three VLANs
mentioned above.
Now let's say that we have assigned Device1 to VLAN Domain "Alpha" (A VLAN Domain that you
had previously created). Upon assignment, "Get VLAN Data" will automatically be run against all
affected equipment, and you would find the following:
• VLANs 10, 20, and 30 -
on the Default VLAN Domain - would exist, and entries for them
would be visible in the "VLANs" portlet.
• "VLANs 10, 20, and 30 -
on the "Alpha" VLAN Domain - would exist , and entries for them
would also be visible in the "VLANs" portlet.
• All VLAN ports/interfaces on Device1 - the device that was assigned to the "Alpha" VLAN
Domain - would have VLAN Membership data visible in the "VLAN Memberships" portlet,
and they would all be associated with the 10, 20, and 30 VLANs -
on the "Alpha" VLAN
Domain
.
• All VLAN ports/interfaces on Device2 - a device that still has no VLAN Domain Assignments
associated with it whatsoever - would have VLAN Membership data placing them in their
appropriate VLANs -
on the "Default" VLAN Domain .
VLAN Domain Inheritance
In order to simplify VLAN Domain assignment, The software incorporates the idea of child
components of a device inheriting VLAN Domain assignment from their parent components. For
example, you are able to assign a specific port/interface to a VLAN Domain, and only that port/
interface will be considered to be assigned to it. If, however, you assign the card - that several ports
are contained in - to a VLAN Domain, all ports on that card will also be assumed to be assigned to
the same VLAN Domain that their parent card is assigned to. This inheritance is supported all the
way up through the top level - i.e., the device itself.
NOTE:
It is possible to have multiple levels of assignment on any given device; however, please note that when
calculating VLAN Membership for a given port/interface, only the first VLAN Assignment found in the
parent/child tree will be used!
For example, if you have assigned a the top level device, "Device1", to VLAN Domain "Alpha", but you
have also individually assigned a port on Device1, "portA", to VLAN Domain "Omega", when VLAN
Membership is calculated for "portA", it will be assumed to be on the "Omega" VLAN Domain, despite
the fact that the device it is contained in - Device1 - is assigned to VLAN Domain "Alpha"!