Single virtual domain fibre channel over ethernet fabric
View Patent ↗The entire FCoE fabric is a single virtual domain, even though there may be multiple FCFs and FDFs. The virtual domain is a different Domain_ID than any of the FCFs. In certain embodiments there are multiple FCFs, of which one is selected as the master or designated FCF. The master FCF performs normal fabric configuration in conjunction with the Fiber Channel fabric. The master FCF assigns the virtual domain FC node IDs and controls development of subdomain IDs. Virtual links are instantiated between the master FCF and other FCFs, between top level FDFs and the FCFs and between the FDFs at each of various levels. FDFs connected to ENodes proxy the master FCF for most FIP operations. FIP FLOGI and FDISC operations are handled by the master FDF, but the FDFs convert the FIP FLOGI requests to VD_FLOGI requests, which include information about the FDF handling the transaction.
1. A Fibre Channel over Ethernet (FCoE) network comprising:
at least one FCoE forwarder (FCF) including a master FCF, wherein each FCF has a Fibre Channel (FC) Domain_ID;
at least one FCoE data forwarder (FDF) coupled to said at least one FCF; and
a plurality of ENodes coupled to said at least one FDF,
wherein said master FCF is responsible for assigning FC IDs to said plurality of ENodes and assigns FC IDs to said plurality of ENodes so that all of said ENodes are addressed as being in a single domain, the Domain_ID of that single domain being different than the Domain_IDs of any FCF of said at least one FCF.
2. The FCoE network of claim 1 , wherein said at least one FCF includes first and second FCFs which are coupled together, and
wherein said first and second FCFs perform operations to determine said master FCF between themselves.
3. The FCoE network of claim 1 , wherein each of the plurality of ENodes provides FCoE Initialization Protocol (FIP) operations directed to said at least one FCF, and
wherein an FDF coupled to an ENode proxies at least some of said FIP operations for said at least one FCF.
4. The FCoE network of claim 3 , wherein said FIP operations proxied include at least one of FIP VLAN discovery and notification, FIP discovery solicitation and advertisement, and FIP unsolicited advertisement and link keep alive.
5. The FCoE network of claim 1 , wherein each of said plurality of ENodes provides FCoE Initialization Protocol (FIP) login requests directed to said at least one FCF,
wherein an FDF coupled to an ENode receives said FIP login requests, converts said FIP login requests to include information identifying the receiving FDF and provides said converted FIP login request to said primary FCF, and
wherein said master FCF replies to said converted FIP login request with a FIP login acceptance identifying the receiving FDF.
6. The FCoE network of claim 5 , wherein said FIP login requests include FIP FLOGI and FIP FDISC.
7. The FCoE network of claim 1 , wherein said at least one FDF includes at least two FDFs coupled in series between an ENode and said primary FCF, the FDF coupled directly and closest to said primary FCF being a top level FDF and the FDFs farther from said primary FCF being lower level FDFs.
8. The FCoE network of claim 7 , wherein said top level FDF cooperates with a next lower level FDF to instantiate a virtual link between said top level FDF and said next lower level FDF.
9. The FCoE network of claim 1 , wherein said at least one FDF includes at least two FDFs coupled together and coupled directly and equally close to said primary FCF, such FDFs being top level FDFs.
10. The FCoE network of claim 9 , wherein said top level FDFs cooperate to instantiate a virtual link between each pair of top level FDFs.
11. The FCoE network of claim 9 , wherein said at least one FDF includes at least three FDFs, at least two FDFs coupled in series between an ENode and said primary FCF, an FDF coupled directly and closest to said primary FCF being a top level FDF and the FDFs farther from said primary FCF being lower level FDFs.
12. The FCoE network of claim 11 , wherein said top level FDF cooperates with a next lower level FDF to instantiate a virtual link between said top level FDF and said next lower level FDF.
13. A Fibre Channel over Ethernet (FCoE) forwarder (FCF) comprising:
at least one Fibre Channel (FC) port for receiving and transmitting FC packets;
at least one FCoE port for receiving and transmitting FCoE packets;
a processor coupled to said at least one FCoE port; and
software executing on said processor, said software causing the FCF to obtain an FC Domain_ID for the FCF and to assign FC addresses in a single domain to any coupled FCoE ENodes, the Domain_ID of said single domain being different than the Domain_ID of the FCF,
wherein said software causes the FCF to reply to a converted FCoE Initialization Protocol (FIP) login request, the converted FIP login request being a normal FIP login request which includes information identifying the receiving FCoE data forwarder (FDF), with a FIP login acceptance identifying the receiving FDF.
14. The FCF of claim 13 , wherein said software causes the FCF to cooperate with any other FCFs to determine the master FCF from among the FCFs.
15. The FCF of claim 13 , wherein normal FIP login requests include FIP FLOGI and FIP FDISC.
16. A Fibre Channel over Ethernet (FCoE) data forwarder (FDF) comprising:
at least one FCoE port for receiving and transmitting FCoE packets;
a processor coupled to said at least one FCoE port; and
software executing on said processor, said software causing the FDF to instantiate a virtual link to an FDF at the same level from the primary Fibre Channel over Ethernet forwarder (FCF) or to an FDF one level away from the level of the FDF.
17. The FDF of claim 16 , wherein said software causes the FDF to instantiate a virtual link between an FDF at the same level from the primary FCF and to an FDF one level away from the level of the FDF.
18. A method comprising:
receiving Fibre Channel (FC) Domain_ID values at Fibre Channel over Ethernet (FCoE) forwarders (FCFs); and
assigning FC IDs to all ENodes in an FCoE fabric so that all of the ENodes are addressed as being in a single domain, the Domain_ID of that single domain being different than the Domain_IDs of any FCF of the FCFs,
replying to a converted FCoE Initialization Protocol (FIP) login request, the converted FIP login request being a normal FIP login request which includes information identifying the receiving FCoE data forwarder (FDF), with a FIP login acceptance identifying the receiving FDF.
19. The method of claim 18 , further comprising:
performing operations by first and second FCFs to determine a master FCF between them.
20. The method of claim 18 , wherein normal FIP login requests include FIP FLOGI and FIP FDISC.
21. A method comprising:
instantiating, by a Fibre Channel over Ethernet (FCoE) data forwarder (FDF), a virtual link to an FDF at the same level from a primary FCoE forwarder (FCF); or
instantiating, by an FDF, a virtual link to an FDF one level away from the level of the FDF.
22. The method of claim 21 , further comprising instantiating, by an FDF, both virtual links.