HP Brocade 8/12c Fabric OS Troubleshooting and Diagnostics Guide v6.4.0 (53-10 - Page 83

Virtual Fabrics, In this General Virtual Fabric troubleshooting

Get HP Brocade 8/12c PDF manuals and user guides View all HP Brocade 8/12c manuals
Add to My Manuals
Save this manual to your list of manuals

Page 83 highlights

Virtual Fabrics Chapter 7 In this chapter •General Virtual Fabric troubleshooting 69 •Fabric identification issues 70 •Logical Fabric issues 70 •Base switch issues 71 •Logical switch issues 72 •Switch configuration blade compatibility 73 General Virtual Fabric troubleshooting All of the following constraints apply when the Virtual Fabric feature is enabled: • The base fabric works only in Brocade native mode, not in an interoperable mode. • The base switch does not have any devices. The base fabric can have devices in remote layer two switches; traffic between those devices is supported. • A non-base switch in a Virtual Fabric-capable chassis must not be part of a fabric that serves as a base fabric for some other logical fabric traffic. Although software will not detect or prevent users from deploying such a configuration, such a configuration is not supported. • ICL ports can only be in the base or default switch. If XISL is turned off, you can connect ICLs to other logical switches. • A default switch can be configured as a base switch in the Brocade 5100 and 5300 switches, but not in a Brocade DCX or DCX-4S. Fabric IDs of default switches cannot be manually changed. • The default switch is able to participate in a logical fabric using extended ISLs (XISLs). In the Brocade DCX and DCX-4S, the default switch will not participate in a logical fabric and will be a purely layer two logical switch. • EX_ and VEX_Ports are supported in the base switch. EX_Ports cannot be part of any other switch other than the base switch. • EX_ and VEX_Ports cannot connect to a fabric that has a logical switch with the Allow XISL use mode on. The port will be disabled with the reason Conflict: XISL capability domain. • Fabric OS v6.2.0 and later support external device sharing only through EX_Ports. Internal device sharing (sharing a device in a logical fabric with other fabrics, without having an EX_Port) is not supported. • A logical fabric cannot have EX_Ports using extended ISLs and cannot serve as a backbone to any EX_Port traffic. Similarly, the default switch cannot be part of a fabric that serves as a backbone to any EX_Port traffic. Fabric OS Troubleshooting and Diagnostics Guide 69 53-1001769-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
Fabric OS Troubleshooting and Diagnostics Guide
69
53-1001769-01
Chapter
7
Virtual Fabrics
In this chapter
•
General Virtual Fabric troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
69
•
Fabric identification issues. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
70
•
Logical Fabric issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
70
•
Base switch issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
71
•
Logical switch issues. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
72
•
Switch configuration blade compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . .
73
General Virtual Fabric troubleshooting
All of the following constraints apply when the Virtual Fabric feature is enabled:
•
The base fabric works only in Brocade native mode, not in an interoperable mode.
•
The base switch does not have any devices. The base fabric can have devices in remote layer
two switches; traffic between those devices is supported.
•
A non-base switch in a Virtual Fabric-capable chassis must not be part of a fabric that serves
as a base fabric for some other logical fabric traffic. Although software will not detect or
prevent users from deploying such a configuration, such a configuration is not supported.
•
ICL ports can only be in the base or default switch. If XISL is turned off, you can connect ICLs to
other logical switches.
•
A default switch can be configured as a base switch in the Brocade 5100 and 5300 switches,
but not in a Brocade DCX or DCX-4S. Fabric IDs of default switches cannot be manually
changed.
•
The default switch is able to participate in a logical fabric
using extended ISLs (XISLs)
. In the
Brocade DCX and DCX-4S, the default switch will not participate in a logical fabric and will be a
purely layer two logical switch.
•
EX_ and VEX_Ports are supported in the base switch. EX_Ports cannot be part of any other
switch other than the base switch.
•
EX_ and VEX_Ports cannot connect to a fabric that has a logical switch with the
Allow XISL use
mode on. The port will be disabled with the reason
Conflict: XISL capability domain
.
•
Fabric OS v6.2.0 and later support external device sharing only through EX_Ports. Internal
device sharing (sharing a device in a logical fabric with other fabrics, without having an
EX_Port) is not supported.
•
A logical fabric cannot have EX_Ports using extended ISLs and cannot serve as a backbone to
any EX_Port traffic. Similarly, the default switch cannot be part of a fabric that serves as a
backbone to any EX_Port traffic.