Dell Brocade 6520 Fabric OS Troubleshooting and Diagnostics Guide v7.1.0 - Page 82

Fabric identification issues, Logical Fabric issues

Get Dell Brocade 6520 PDF manuals and user guides View all Dell Brocade 6520 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 82 highlights

7 Fabric identification issues • VE_Ports cannot exist in a logical switch that has XISL use turned on. Although VE_Ports are allowed in a base switch, Fabric OS v6.2.0 and later do not support the use of VE_Ports to carry traffic for logical fabrics using XISLs. They can be used to carry FCR traffic through EX_Ports and VEX_Ports. You should make sure your configuration does not result in the use of VE_Ports in a base switch for logical fabric traffic. • Admin Domains are mutually exclusive with Virtual Fabrics. When Virtual Fabrics is enabled, all access control is based on the Virtual Fabric context. • Traffic Isolation zones with no-failover option are not supported in logical fabrics. TI zones defined in the base fabric for logical fabric traffic must allow failover. NOTE A new option "Disable FID check" has been added to configure fabric parameter options. This can be used to disable FID check for FICON logical switches. Fabric identification issues Symptom Symptom Symptom E_Ports directly connecting two logical switches do not form, or are disabled. Probable cause and recommended action The FIDs on each of the logical switches must be the same. Use the lsCfg --show command to view the current FIDs on the chassis and then the lsCfg --change FID -newfid FID command to change the FID. Invalid FID. Probable cause and recommended action FIDs for switches may be from 1 through 128 as long as they are not already in use, except for EX_Ports, which are only assigned FIDs from 1 through 127. Use the lsCfg --show command to verify whether the FID is in use. If it is, use another FID. The FID is currently in use. Probable cause and recommended action You may not create two (2) or more logical switches with the same FID. Use the lsCfg --show and fcrFabricShow commands to view FIDs in use. Logical Fabric issues Symptom Logical port disabled. Probable cause and recommended action This message indicates an LISL was disabled because of some protocol conflict or security or policy violation. This can result in possible traffic issues. You should resolve the cause of the conflict and reenable the LISL by using the lfCfg --lislenable command. 66 Fabric OS Troubleshooting and Diagnostics Guide 53-1002751-01

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
66
Fabric OS Troubleshooting and Diagnostics Guide
53-1002751-01
Fabric identification issues
7
•
VE_Ports cannot exist in a logical switch that has XISL use turned on. Although VE_Ports are
allowed in a base switch, Fabric OS v6.2.0 and later do not support the use of VE_Ports to
carry traffic for logical fabrics using XISLs. They can be used to carry FCR traffic through
EX_Ports and VEX_Ports. You should make sure your configuration does not result in the use of
VE_Ports in a base switch for logical fabric traffic.
•
Admin Domains are mutually exclusive with Virtual Fabrics. When Virtual Fabrics is enabled, all
access control is based on the Virtual Fabric context.
•
Traffic Isolation zones with no-failover option are not supported in logical fabrics. TI zones
defined in the base fabric for logical fabric traffic must allow failover.
NOTE
A new option “Disable FID check” has been added to configure fabric parameter options. This can
be used to disable FID check for FICON logical switches.
Fabric identification issues
Symptom
E_Ports directly connecting two logical switches do not form, or are disabled.
Probable cause and recommended action
The FIDs on each of the logical switches must be the same.
Use the
lsCfg
--
show
command to view the current FIDs on the chassis and then the
lsCfg
--
change
FID
-newfid
FID
command
to change the FID.
Symptom
Invalid FID.
Probable cause and recommended action
FIDs for switches may be from 1 through 128 as long as they are not already in use, except for
EX_Ports, which are only assigned FIDs from 1 through 127.
Use the
lsCfg
--
show
command to verify whether the FID is in use. If it is, use another FID.
Symptom
The FID is currently in use.
Probable cause and recommended action
You may not create two (2) or more logical switches with the same FID.
Use the
lsCfg
--
show
and
fcrFabricShow
commands to view FIDs in use.
Logical Fabric issues
Symptom
Logical port <port_number> disabled.
Probable cause and recommended action
This message indicates an LISL was disabled because of some protocol conflict or security or policy
violation. This can result in possible traffic issues. You should resolve the cause of the conflict and
reenable the LISL by using the
lfCfg
--
lislenable
command.