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

Configuring Profiles Configuring Universal Network Profiles
page 27-34 OmniSwitch AOS Release 7 Network Configuration Guide June 2013
Although SAA profiles can be configured and assigned to a UNP through the CLI, these profiles are
mainly used by the Alcatel-Lucent OmniVista network management application to monitor connections
between virtual machines (VMs) in a data center network.
Configuring Service Classification Profiles
A profile name, VLAN tag value, service instance ID (I-SID), and backbone VLAN (BVLAN) ID are
required service profile attributes. Optional profile attributes include classification rules and a QoS policy
list name.
Consider the following when configuring a service profile:
•
The VLAN tag value indicates if the VLAN tag information from the classified packets is used to
assign the traffic to a service access point (SAP) or if specific single or double-tag values are used to
assign the traffic to a SAP. Specify one of the following VLAN tag values for the profile:
•
If classified traffic is untagged then zero is used for the SAP encapsulation value (for example, 1/2:0).
•
If the I-SID value specified does not exist in the switch configuration, the service is dynamically
created first then the SAP is dynamically created and associated with this service.
•
The BVLAN associated with a profile must already exist in the switch configuration.
•
If the VLAN tag value of the classified traffic does not match the tag value specified in the profile,
UNP will check to see if the trust VLAN tag option is enabled for the access port. If so, a SAP is
assigned using the VLAN tag values of the traffic. If not, the traffic is learned as filtering on the port.
•
Two other configurable service profile attributes include specifying the multicast replication mode
(head-end or tandem) and the egress VLAN translation status for the SPB service associated with the
profile. By default, the head-end mode is applied and VLAN translation is disabled.
>
When the head-end multicast mode is used, a non-unicast packet received on an SPB access port is
replicated once for each receiver in the provider backbone bridge (PBB) network using its unicast
base MAC (BMAC) address.
>
When the tandem multicast mode is used, a non-unicast packet received on an SPB access port is
replicated once at each node using the multicast group address.
>
Enabling VLAN translation at the service level is only applicable if the corresponding access ports
for the SAPs also have VLAN translation enabled.
•
Service profile attributes are only applied to device traffic that is received on UNP-enabled access ports
(see
“Enabling UNP on Ports” on page 27-28 ).
•
Specifying a QoS policy list name that is inactive or does not already exist in the switch configuration
is allowed. However, the list will remain inactive for the UNP until the list is enabled or configured
using the QoS policy list commands (see
“Configuring QoS Policy Lists” on page 27-37 ).
0 (zero) The VLAN tag of the packet is used to determine the SAP encapsu-
lation value. Setting the profile tag value to zero has the same result
as enabling trust VLAN tag for the access port.
Outer VLAN tag The outer VLAN tag value to use for the SAP encapsulation value.
Inner and outer VLAN tags The inner and outer VLAN tag values to use for the SAP encapsu-
lation value.