HP StorageWorks Fabric OS 6.2 administrator guide (5697-0016, May 2009)

396 Using the FC-FC routing service
FC router matrix definition
Depending on how the backbone fabric is structured, you can specify pairs of FC routers that can access
each other. For the metaSAN shown in Figure 66 on page 394, the following FC routers can access each
other:
• FC router 1 and FC router 2
• FC router 3 and FC router 4
Because there is no device sharing between the two groups of FC routers, you can use the
fcrLsanMatrix command with the -fcr option to create the corresponding FC router matrix:
fcrlsanmatrix --add -fcr wwn1 wwn2
fcrlsanmatrix --add -fcr wwn3 wwn4
where wwn1, wwn2, wwn3, and wwn4 are the WWNs of the four FC routers.
Now edge fabrics 1, 2, 3, 7, and 8 can access each other, and edge fabrics 4, 5, 6, and 9 can access
each other; however, edge fabrics in one group cannot access edge fabrics in the other group.
LSAN fabric matrix definition
With LSAN zone binding, you can specify pairs of fabrics that can access each other. Using the metaSAN
shown in Figure 66 on page 394 as an example, the following edge fabrics can access each other:
• Fabric 1 and Fabric 2
• Fabric 2 and Fabric 3
• Fabric 4 and Fabric 5
• Fabric 5 and Fabric 6
You can use the fcrLsanMatrix command with the -lsan option to create the corresponding LSAN
fabric matrix:
fcrlsanmatrix --add -lsan 1 2
fcrlsanmatrix --add -lsan 2 3
fcrlsanmatrix --add -lsan 4 5
fcrlsanmatrix --add -lsan 5 6
Fabrics that are not specified are part of the default binding and can access other edge fabrics that are not
specified. So Fabrics 7, 8, and 9 can access each other, but cannot access Fabrics 1 through 6.
CAUTION: The command fcrLsanMatrix --add -lsan 0 0 erases the entire LSAN fabric matrix
settings in the cache.
The FC router matrix and the LSAN fabric matrix are used together to determine which fabrics can access
each other, with the LSAN fabric matrix providing more specific binding.
Upgrade, downgrade, and HA considerations for LSAN zone binding
When a CP is upgraded from Fabric OS 6.0.x or 5.3.x to 6.1.0, the LSAN zone binding and handling
remains the same. Fabric-wide distribution does not occur until the database is changed and activated.
When a CP is downgraded from Fabric OS 6.1.0 where the FC router matrix feature is activated to 6.0.x or
5.3.x firmware that does not support that feature, the firmwareDownload script prompts you to delete
the FC router matrix binding entries prior to the firmware downgrade.
If the active CP is running Fabric OS 6.1.0 and the standby CP is running 6.0.x or 5.3.x, the FC router
matrix feature will not be activated. You will get an error message if you try to update the FC router matrix
information.
If the active CP is running Fabric OS 6.1.0 and the FC router matrix is activated and the standby CP
running 6.0.x or 5.3.x comes online later, the active CP will not establish HA sync with the standby CP
during the sync dump operation.