OmniSwitch os6900, Руководство по настройке сети, Страница: 712 / 942

UNP Overview Configuring Universal Network Profiles
page 27-12 OmniSwitch AOS Release 7 Network Configuration Guide June 2013
UNP Port Types
By default, all switch ports are non-UNP (fixed) ports that are statically assigned to a specific VLAN.
Once UNP is enabled on a port, traffic from each device connected to that port is classified using the UNP
port and profile configuration to determine the VLAN or SPB service assignment for the device.
There are two types of UNP ports: bridge and access. The port type is specified when UNP functionality is
enabled on the port. If a port is configured as a UNP bridge port, then traffic received on that port is only
classified using VLAN profiles. If a port is configured as a UNP access port, then traffic received on that
port is only classified using SPB service profiles.
The port type basically determines if device traffic received on that port is classified into the VLAN
domain or the SPB service domain.
When a UNP bridge port is dynamically assigned to a VLAN, a VLAN port association (VPA) is created
and tracked by VLAN management software on each switch. Because the UNP configuration is applied to
each device connected or forwarded through a UNP port, the UNP port can associate with more than one
VLAN.
UNP access ports are not dynamically assigned to VLANs. Instead, traffic received on the port is classi-
fied to a SPB a service access point (SAP). A SAP is a virtual port that maps classified device traffic to a
SPB service.
Customer Domains
UNP customer domains provide an additional method for segregating device traffic. A domain is identi-
fied by a numerical ID, which can be assigned to UNP ports and profile classification rules. By default, all
UNP ports (bridge and access) and profile rules are assigned to domain 0.
The main benefit of customer domains is that they provide the ability to group physical UNP ports or link
aggregates into one logical domain. Once a UNP port is assigned to a specific customer domain ID, only
classification rules associated with the same domain ID are applied to that port.
An example of using customer domains would be to group UNP ports carrying traffic for a specific
customer into the same domain (all Customer A ports assigned to domain 2). Then assign VLAN and/or
service profiles tailored for that customer to the same domain ID (all profiles for Customer A assigned to
domain 2).
UNP VLANs
When a VLAN UNP is created, specifying a VLAN ID is required. Traffic that is classified with the UNP
is assigned to the associated VLAN. There are two methods for creating this type of VLAN:
•
Using standard VLAN management commands, create the VLAN then assign the VLAN to the UNP at
the time the profile is created.
•
Enabling the UNP dynamic VLAN configuration option to automatically create the VLAN, if it does
not exist, at the time the UNP is created.
VLANs that are automatically created at the time the profile is created are referred to as UNP dynamic
VLANs. These VLANs carry many of the same attributes as standard VLANs, such as:
•
The VLAN status (enabled or disabled) is configurable.
•
Additional ports (tagged and untagged) can be assigned to dynamic VLANs.