HP AE370A - Brocade 4Gb SAN Switch 4/12, Руководство администратора

Страница: 219 / 447

Fabric OS 5.2.x administrator guide 219
On the 4/256 SAN Director with a B-Series MP Router blade, the host and fabric75 are imported,
because both are defined by lsan_zone_fabric2 and lsan_zone_fabric75 . However, target B defined by
lsan_zone_fabric75 is not imported because lsan_zone_fabric2 does not allow it.
When a PLOGI, PDISC, or ADISC arrives at the 4/256 SAN Director with a B-Series MP Router blade, the
SID and DID of the frame are checked. If they are LSAN-zoned at both SID and DID edge fabrics, the frame
will be forwarded to the DID. If they are not zoned, only the PLOGI is dropped; for the remaining frames
zoning enforcement takes place in the edge fabrics.
You can also set up LSAN zones using the following procedure.
To set up LSAN zones
1. Create a telnet or Web Tools connection to the switch.
2. Configure the LSAN, using the LSAN_xxxx naming schema, and append the new LSAN to the active
zone set.
3. Enable zone configuration that now includes the new LSAN.
Configuring backbone fabrics for Interconnectivity
If you want devices in backbone fabrics to communicate with devices in edge fabrics, follow the steps in
the preceding section, but instead of configuring the LSAN for the second edge fabric, do so for the
backbone fabric.
Optional configuration procedures
This section describes optional configuration procedures; none are required to set up the FC-FC Routing
Service.
FC router port cost (optional)
In Fabric OS v5.2.x, FCR optimizes the usage of the router port links by directing the traffic to the link with
the smallest router port cost. The FC router port cost is similar to the link cost setting available on E_Ports,
which allows the user to customize traffic flow. The router port link cost values are either 1000 or 10,000.
The router module chooses the router port path based on the lowest cost per FID connection. If multiple
paths exist with the same lowest cost, there will be load sharing over these paths.
You need only to differentiate between VEX and EX_Port link going to the same edge fabric as VEX and
EX_Ports have very different speeds. For example, if there are VEX and EX_Port connections to the same
edge fabric, the traffic is directed through the EX_Port link.
Every IFL has a default cost. The default router port cost values are:
• 1000 for legacy (v5.1 or XPath FCR) IFL
• 1000 for EX_Port IFL
• 10,000 for VEX_Port IFL
The FCR router port cost settings are 0, 1000 or 10,000. If the cost is set to 0, the default cost will be
used for that IFL. The FC router port cost is persistent and is saved in the existing port configuration file.
Router port cost is passed to other routers in the same backbone. Link costs from the front domain to the
translate (xlate) domain remain at 10,000. You can use the
lsDbShow
from the edge fabric to display
these link costs.
Using router port cost
Initially, the router port cost value for an EX_Port is set when the EX_Port is created when the
portCfgExport
command is issued. However, you can use the
fcrRouterPortCost
to modify the
cost for that port. You can configure the EX or VEX_Port with either 1000 or 10,000 values. If you wish to
differentiate between two EX_Port links with different speeds, you can assign 1000 to one link and 10,000
to another link.
For details about the use of any of the following commands, see the
Fabric OS Command Reference
Manual .