FW 08.01.00 McDATA E/OS Command Line Interface User Manual (620-000134-740, November 2005)

CLI Commands

2-53

config

----------- ----------- -------------

johndoe_1223 Web,CLI Administrator

ewsOperator Web Operator

Operator Web,CLI Operator

config.security.fabricBinding

Fabric Binding functionality provided by the SANtegrity Binding

feature allows you to bind the switch or director to specified fabrics

so that it can communicate only with those fabrics included in the

Fabric Binding Membership List (FBML). This provides security from

accidental fabric merges and potential fabric disruption when fabrics

become segmented because they cannot merge.

Fabric Binding

Commands

The config.security.fabricBinding commands function in a different

way from most CLI commands, which are single action commands

that take effect immediately. Most of the Fabric Binding commands

affect a temporary copy of an FBML in the work area called the

Pending FBML. When this temporary copy is activated to the fabric,

it is called the Active FBML.

ATTENTION! The EFCM Basic interface can change Fabric Binding status

and FBMLs if it is used at the same time as the CLI.

Because not all the verification of the Pending FBML can occur on the

temporary copy in the work area, it is possible, however unlikely,

that the copy of the list encounters no errors until the list is activated

to the fabric.

NOTE: A Sphereon 4300 Switch cannot participate in a fabric, unless the

Fabric Capable feature is enabled. For more information, see the McDATA

Sphereon 4300 Switch Installation and Service Manual (620-000171).

Fabric Binding

Membership

Terminology

Two types of FBMLs are configured using the CLI:

• Active FBML: When fabric binding is active, the active FBML is

the list of fabric members with which the product is allowed to

communicate. If fabric binding is disabled, this list is empty.

• Pending FBML: A list used to configure an FBML before it is

made active on the director or switch. Changes to the pending

FBML are not implemented in the fabric until they are saved and

activated using the config.security.fabricBinding.activatePending

command as documented on page 2-54.