S e n d f e e d b a c k t o n x 5 0 0 0 - d o c f e e d b a c k @ c i s c o . c o m
43-7
Cisco Nexus 5000 Series Switch CLI Software Configuration Guide
OL-16597-01
Chapter 43 Advanced Fibre Channel Features and Concepts
FC ID Allocation for HBAs
FC ID Allocation for HBAs
Fibre Channel standards require a unique FC ID to be allocated to an N port attached to an F port in any
switch. To conserve the number of FC IDs used, Cisco Nexus 5000 Series switches use a special
allocation scheme.
Some HBAs do not discover targets that have FC IDs with the same domain and area. The switch
software maintains a list of tested company IDs that do not exhibit this behavior. These HBAs are
allocated with single FC IDs. If the HBA can discover targets within the same domain and area, a full
area is allocated.
To allow further scalability for switches with numerous ports, the switch software maintains a list of
HBAs that can discover targets within the same domain and area. Each HBA is identified by its company
ID (also known as Organizational Unique Identifier, or OUI) used in the pWWN during a fabric log in.
A full area is allocated to the N ports with company IDs that are listed and for the others, a single FC ID
is allocated. Regardless of the type (whole area or single) of FC ID allocated, the FC ID entries remain
persistent.
This section includes the following topics:
•
Default Company ID List, page 43-7
•
Verifying the Company ID Configuration, page 43-8
Default Company ID List
All Cisco Nexus 5000 Series switches contain a default list of company IDs that require area allocation.
Using the company ID reduces the number of configured persistent FC ID entries. You can configure or
modify these entries using the CLI.
Caution
Persistent entries take precedence over company ID configuration. If the HBA fails to discover
a target, verify that the HBA and the target are connected to the same switch and have the same
area in their FC IDs, then perform the following procedure:
1. Shut down the port connected to the HBA.
2. Clear the persistent FC ID entry.
3. Get the company ID from the port WWN.
4. Add the company ID to the list that requires area allocation.
5. Bring up the port.
The list of company IDs have the following characteristics:
•
A persistent FC ID configuration always takes precedence over the list of company IDs. Even if the
company ID is configured to receive an area, the persistent FC ID configuration results in the
allocation of a single FC ID.
•
New company IDs added to subsequent releases are automatically added to existing company IDs.
•
The list of company IDs is saved as part of the running and saved configuration.
•
The list of company IDs is used only when the fcinterop FC ID allocation scheme is in auto mode.
By default, the interop FC ID allocation is set to auto, unless changed.
Summary of Contents for N5010P-N2K-BE
Page 50: ...Se n d f e e d b a ck t o n x 5 0 0 0 d o c f e e d b a ck c i s c o c o m ...
Page 102: ...Se n d f e e d b a ck t o n x 5 0 0 0 d o c f e e d b a ck c i s c o c o m ...
Page 240: ...Se n d f e e d b a ck t o n x 5 0 0 0 d o c f e e d b a ck c i s c o c o m ...
Page 312: ...Se n d f e e d b a ck t o n x 5 0 0 0 d o c f e e d b a ck c i s c o c o m ...
Page 400: ...Se n d f e e d b a ck t o n x 5 0 0 0 d o c f e e d b a ck c i s c o c o m ...
Page 418: ...Se n d f e e d b a ck t o n x 5 0 0 0 d o c f e e d b a ck c i s c o c o m ...
Page 436: ...Se n d f e e d b a ck t o n x 5 0 0 0 d o c f e e d b a ck c i s c o c o m ...
Page 658: ...Se n d f e e d b a ck t o n x 5 0 0 0 d o c f e e d b a ck c i s c o c o m ...