Life of a port-profile – Brocade Network OS Administrator’s Guide v4.1.1 User Manual
Page 330
In addition, all the combinations can be mixed up with some security rules grouped under a security-
profile.
NOTE
A port-profile does not contain some of the interface level configurations, such as LLDP, SPAN, LAG,
and so on.
A port-profile operates as a self-contained configuration container. In other words, if a port-profile is
applied on a completely new switch without any configuration, it is capable of configuring the
interface’s local configuration and starting to carry traffic. Any changes to the policies are immediately
applied to the data plane.
Security profiles are applied to the ACLs based on the profile or PolicyID. Therefore, multiple security
profiles can be applied to the same profiled port, except on the Brocade VDX 6730.
NOTE
The fcoe-profile is only available on the default profile. User-defined port-profiles do not have access
to the fcoe-profile. However, editing of the port-profile is not allowed once the port-profile is activated.
Activation of the port-profile is mandatory when it is applied to a port. Refer to
on page 333 for additional details.
Life of a port-profile
A port-profile during creation will go through multiple states. The states of a port-profile are as follows:
• Created —This state specifies that a port-profile is created or modified, but may not be complete.
• Activated —This state specifies that a port-profile is activated and is available for MAC->port-profile
association. If the port-profile created is not complete then the activation fails; you must resolve any
conflicts or dependencies and reactivate the port-profile.
• Associated —This state specifies that one or more MAC addresses have been associated to this
port-profile within the fabric.
• Applied —This state indicates that the port-profile is applied on the profiled port where the
associated MAC address appeared. In the absence of any signaling protocol, the system snoops
the packet to detect if the associated MAC address has appeared on the profiled port. Configuration
of two different port-profiles can co-exist on a profiled port, but if there is a conflict then the
application of the later port-profile fails.
The following table describes the AMPP events and the applicable failure behaviors.
AMPP behavior and failure descriptions
TABLE 56
AMPP event
Applicable behavior and failures
Create port-profile
• If the port-profile does not exist, then it is created. If it exists, then it is
available for modification (if it is not yet activated).
Activate port-profile
• If the port-profile configuration is not complete, activation fails. Unless the port-
profile is activated, it is not applied on any port-profile-port.
• If all the dependency validations succeed, the port-profile is in the ACTIVE
state and is ready for association.
• A vlan-profile is mandatory for all port-profiles.
Life of a port-profile
330
Network OS Administrator’s Guide
53-1003225-04