Fabric os command limitations and considerations – Brocade FICON Administrator’s Guide (Supporting Fabric OS v7.3.0) User Manual

Page 59

Advertising
background image

Access to switch configuration parameters is serialized.

The active CUP configuration data, including the following, is initialized according to the IPL file:

Port and switch names

Port "Block" and "Unblock" values

PDCM values

Brocade Advanced Zoning, if used, continues to be in force. If there are any differences between
the port-to-port connectivity restrictions defined by Brocade Advanced Zoning and those defined by
PDCMs, the most restrictive rules are automatically applied.

RSCNs are sent to devices if PDCM changes result in changes to connectivity between a set of
ports that are zoned together.

An RSCN for the CUP is generated to all mainframe FICON and FCP channels in the fabric.

Changing FMS mode from enabled to disabled triggers the following events:

A device reset is performed on the control device.

Prohibits are no longer enforced.

RSCNs may be generated to some devices if PDCM removal results in changes to connectivity
between a set of ports that are zoned together.

If a given port was set to "Block" or "Unblock," that port remains disabled or enabled.

The switch interface for host in-band management is no longer enabled.

An RSCN for the CUP is generated to all mainframe FICON and FCP channels in the fabric.

NOTE
FMS mode cannot be enabled in a Virtual Fabrics environment when a logical switch is using Mode 0
addressing.

Fabric OS command limitations and considerations

This section describes limitations and considerations for using Fabric OS commands with FMS mode
enabled. For a list of Fabric OS commands related to FICON, refer to

FICON commands

on page 28.

The following Fabric OS commands return a "switch busy" response if they are issued when the
host-based management application is performing a write operation. This prevents interference
from out-of-band management applications when a host-based management program is being
used to administer the switch.

bladeEnable

portName

portShow

portSwap

switchCfgPersistentDisable

switchDisable

switchEnable

switchName

switchShow

portDisable

portEnable

You cannot use the portCfgPersistentEnable and portCfgPersistentDisable commands to
persistently enable and disable ports. Refer to

Persistently enabling and disabling ports for CUP

on

page 64 for instructions.

Specifying a range of ports for the portName command will fail except for the first port in the range.
FMS mode does not permit multiple ports with the same name.

Fabric OS command limitations and considerations

FICON Administrator's Guide

57

53-1003144-01

Advertising