beautypg.com

Dell POWEREDGE M1000E User Manual

Page 323

background image

Fabric OS Command Reference

291

53-1001764-02

fcrLsanMatrix

2

52 10:32:16:90:28:dd:d0:03 0bf001 82 2a0900 Imported

52 10:32:16:91:24:dd:d0:07 0bf002 82 520c00 Imported

52 10:32:16:91:25:dd:d0:06 01f002 78 4e3000 Imported

78 10:00:00:06:2b:0d:29:31 09f002 52 482200 Imported

78 10:32:16:90:29:dd:d0:07 08f002 82 2a0a00 Imported

78 10:32:16:91:24:dd:d0:05 09f001 52 48a100 Imported

78 10:32:16:91:25:dd:d0:03 08f001 82 520f00 Imported

82 10:00:00:06:2b:0d:29:30 01f002 78 4e1400 Imported

82 10:00:00:06:2b:0d:2f:ed 03f002 52 480200 Imported

82 10:00:00:06:2b:0d:33:4d 01f001 78 4e1800 Imported

82 10:00:00:06:2b:0e:4d:c9 03f001 52 482000 Imported

Total devices displayed: 12

To display the information from the cache:

switch:admin >

fcrlsanmatrix --display -lsan

Fabric ID 1 Fabric ID 2

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

52 78

52 82

78 82

To apply the changes persistently:

switch:admin >

fcrlsanmatrix --apply -lsan

To view all the static and the default/dynamic fabric binding in the backbone:

switch:admin >

fcrlsanmatrix --fabricview -lsan

LSAN MATRIX is activated

Fabric ID 1 Fabric ID 2

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

52 78

52 82

78 82

Default LSAN Matrix:

57 91

Diagnostics

Error message (1):

"LSAN Matrix in the cache conflicts with existing import/export devices and may disrupt traffic."

"Please refer to the man page for the corrective action."

Corrective actions:

Any new router added to backbone fabric automatically triggers a matrix merge. If a router
does not support the matrix merge feature, the router can not join the backbone fabric. Make
sure that all legacy FCR switches in the backbone support the matrix merge feature, otherwise
the feature is not supported.

Use fcrlsanmatrix

--

fabricview -lsan | -fcr to confirm that all the switches in the backbone

have the same LSAN and FCR binding matrix. If not, there are two solutions. The first solution
is to modify one FCR or both to make them the same and then activate the FCRs. The second
solution is to zero out the database of one FCR to signal that this FCR accepts the database
from the other FCR once the change is activated.