Reference Guide

FIGURE 82 Example of setting up Enforce LSAN tag
FC router 1 does not need to know about the LSAN between edge fabrics 2 and 3. Likewise, FC router 3 does not need to know about
the LSAN between edge fabrics 1 and 2.
In this scenario, you could set up two Enforce tags, one for each LSAN. On FC router 2, both Enforce tags would be needed, since FC
router 2 uses both LSANs. FC router 1 and FC router 3 each need only one tag, for their respective LSANs.
Setting up Enforce tags in this way keeps resources on FC router 1 and FC router 3 at a minimum. This is a simple example, but could
become more complex as more FIDs are added to each FC router or as additional FC routers are added to the backbone.
How the Enforce tag works
The FC router automatically accepts all zones with names that start with "lsan_". You can specify an Enforce tag to indicate that a
particular FC router should accept only zones that start with the prefix "lsan_ tag ". For example, if you specify an Enforce tag of "abc", the
FC router accepts only those LSAN zones that start with "lsan_abc" and does not import or export any other LSAN zones.
The Enforce tag can be up to eight characters long and can contain only letters and numbers.
The Enforce tag is not case-sensitive; for example, the tag "abc" is equivalent to "ABC" and "Abc".
If you specify "abc", "xyz", and "fab1" as Enforce tags, then the FC router accepts only those LSAN zones with names that start with any of
the following:
∙ lsan_abc
∙ lsan_xyz
∙ lsan_fab1
In this example, the following LSAN zones would all be accepted:
∙ lsan_abc
∙ Lsan_xyz123456
Using FC-FC Routing to Connect Fabrics
Brocade Fabric OS Administration Guide, 8.0.1
524 53-1004111-02