OmniSwitch os6900 Network Configuration Manual page 711

Configuring Universal Network Profiles
policy list is allowed per profile, but multiple profiles may use the same policy list. See
QoS Policy Lists" on page 27-37
The service profile attributes (VLAN tag, I-SID, and BVLAN) are used to define an SPB service access
point (SAP) for traffic that is classified by the service profile.
•
The VLAN tag combined with the local UNP access port, on which matching profile traffic is received,
specifies the encapsulation value for the SAP.
•
The I-SID and BVLAN ID specify a backbone service for the SAP and is the service that will forward
the matching profile traffic through the network.
For more information about SPB services and SAPs, see
ing," in the OmniSwitch AOS Release 7 Data Center Switching Guide
Dynamic SAP Configuration
When device traffic is assigned to a service profile, UNP first checks the switch configuration to see if a
SAP already exists for the VLAN tag, I-SID, and BVLAN ID values as defined in the service profile. If a
SAP already exists with these values, the device traffic is classified into that SAP. If the SAP does not
exist, the switch dynamically creates one for the profile traffic. In addition:
>
If the I-SID value specified in the service profile does not exist, the switch will dynamically create
the expected service and then the SAP as needed. This is similar to functionality in the VLAN
domain, where UNP will dynamically create a VLAN based on the 802.1Q-tag of the device traffic.
>
If the BVLAN ID specified in the service profile does not exist, the dynamic SAP is not created.
UNP also provides dynamic SAP configuration for UNP access port traffic that is not classified by a UNP
service profile. Because there is no service profile associated with this traffic, UNP derives the necessary
SAP parameters using the following system parameter values and calculations:
•
The SPB control BVLAN configured for the switch serves as the BVLAN for the dynamic SAP.
•
The UNP customer domain ID for the UNP access port and a base I-SID number (10,000). By default,
all UNP ports are assigned to customer domain 0.
•
The base system I-SID number and the customer domain ID are used in the following calculations to
determine the default system I-SID value to use for the dynamic SAP:
>
If the UNP customer domain ID is from 0 to 255, then the default system I-SID value is
(customer domain ID * 10,000). For example, if the customer domain ID is 200, then the default system I-SID value
used is 12,000,000.
>
If the UNP customer domain ID is from 256 to 511, then the default system I-SID value is
10,000,000 + (customer domain ID * 10,000) + (outer VLAN tag of the packet). For example, if the
customer domain ID is 500 and the outer VLAN tag of the access port traffic is 100, then the default
system I-SID value used is 15,000,100.
•
A reserved SPB service ID (32768) that represents the association between the default system I-SID
and the control BVLAN. This value increments by 1 for each additional dynamic service that is created
and only has local significance.
Dynamically creating services and related SAPs is subject to available switch resources. If an attempt to
dynamically create a service or SAP fails, for any reason, the MAC addresses classified for the service
profile are learned as filtering.
Note. Dynamically created SAPs are not saved to the switch configuration file.
OmniSwitch AOS Release 7 Network Configuration Guide
for more information.
Chapter 3, "Configuring Shortest Path Bridg-
June 2013
UNP Overview
"Configuring
10,000,000 +
page 27-11