Fabric OS Administrator’s Guide
65
53-1001763-02
Routing overview
4
FSPF makes minimal use of the ISL bandwidth, leaving virtually all of it available for traffic. In a
stable fabric, a switch transmits 64 bytes every 20 seconds in each direction. FSPF frames have
the highest priority in the fabric. This guarantees that a control frame is not delayed by user data
and that FSPF routing decisions occur very quickly during convergence.
FSPF guarantees a routing loop free topology at all times. It is essential for a fabric to include many
physical loops because without loops there would be no multiple paths between switches, and
therefore no redundancy. If a link went down, part of the fabric becomes isolated. FSPF ensures
that the topology is loop free and that the frame is never forwarded over the same ISL more than
once.
FSPF calculates paths based on the destination domain ID. The fabric protocol must complete
domain ID assignments before routing can begin. ISLs provide the physical pathway when the
Source ID (SID) address has a frame destined to a port on a remote switch Destination ID (DID).
When an ISL is attached or removed from a switch, the FSPF updates the route tables to reflect the
addition or deletion of the new routes.
As each host transmits a frame to the switch, the switch reads the SID and DID in the frame
header. If the domain ID of the destination address is the same as the switch (intra-switch
communications), the frame buffer is copied to the destination port and a credit R_RDY is sent to
the host. The switch only needs to read word zero and word one of the Fibre Channel frame to
perform what is known as cut-through routing. A frame may begin to emerge from the output port
before it has been entirely received by the input port. The entire frame does not need to be
buffered in the switch.
If the destination domain ID is different than the source domain ID, then the switch consults the
FSPF route table to identify which local E_Port provides the Fabric Shortest Path First to the remote
domain.
Fibre Channel NAT
Within an edge fabric or across a backbone fabric, the standard Fibre Channel fabric shortest path
first (FSPF) protocol determines how frames are routed from the source Fibre Channel device to the
destination FC device. The source or destination device can be a proxy device.
Fibre Channel fabrics require that all ports be identified by a unique PID. In a single fabric, FC
protocol guarantees that domain IDs are unique, and so a PID formed by a domain ID and area ID is
unique within a fabric. However, the domain IDs and PIDs in one fabric may be duplicated within
another fabric, just as IP addresses that are unique to one private network are likely to be
duplicated within another private network.
In an IP network, a network router can maintain network address translation (NAT) tables to replace
private network addresses with public addresses when a packet is routed out of the private
network, and to replace public addresses with private addresses when a packet is routed from the
public network to the private network. The Fibre Channel routing equivalent to this IP-NAT is the
Fibre Channel network address translation (FC-NAT). Using FC-NAT, the proxy devices in a fabric can
have PIDs that are different from the real devices they represent, allowing the proxy devices to have
appropriate PIDs for the address space of their corresponding fabric.
Содержание 53-1001763-02
Страница 1: ...53 1001763 02 13 September 2010 Fabric OS Administrator s Guide Supporting Fabric OS v6 4 0 ...
Страница 4: ...iv Fabric OS Administrator s Guide 53 1001763 02 ...
Страница 24: ...xxiv Fabric OS Administrator s Guide 53 1001763 02 ...
Страница 28: ...xxviii Fabric OS Administrator s Guide 53 1001763 02 ...
Страница 32: ...xxxii Fabric OS Administrator s Guide 53 1001763 02 ...
Страница 40: ...xl Fabric OS Administrator s Guide 53 1001763 02 ...
Страница 42: ...2 Fabric OS Administrator s Guide 53 1001763 02 ...
Страница 54: ...14 Fabric OS Administrator s Guide 53 1001763 02 High availability of daemon processes 1 ...
Страница 74: ...34 Fabric OS Administrator s Guide 53 1001763 02 Basic connections 2 ...
Страница 102: ...62 Fabric OS Administrator s Guide 53 1001763 02 Audit log configuration 3 ...
Страница 156: ...116 Fabric OS Administrator s Guide 53 1001763 02 The authentication model using RADIUS and LDAP 5 ...
Страница 214: ...174 Fabric OS Administrator s Guide 53 1001763 02 Management interface security 7 ...
Страница 228: ...188 Fabric OS Administrator s Guide 53 1001763 02 Brocade configuration form 8 ...
Страница 276: ...236 Fabric OS Administrator s Guide 53 1001763 02 Creating a logical fabric using XISLs 10 ...
Страница 404: ...364 Fabric OS Administrator s Guide 53 1001763 02 ...
Страница 440: ...400 Fabric OS Administrator s Guide 53 1001763 02 Performance data collection 17 ...
Страница 464: ...424 Fabric OS Administrator s Guide 53 1001763 02 Disabling bottleneck detection on a switch 18 ...
Страница 480: ...440 Fabric OS Administrator s Guide 53 1001763 02 F_Port masterless trunking 19 ...
Страница 494: ...454 Fabric OS Administrator s Guide 53 1001763 02 Buffer credit recovery 20 ...
Страница 560: ...520 Fabric OS Administrator s Guide 53 1001763 02 Port indexing on the Brocade DCX 4S backbone C ...
Страница 574: ...534 Fabric OS Administrator s Guide 53 1001763 02 Hexadecimal overview E ...