Brocade Communications Systems BR-1020 Instrukcja Naprawy Strona 48

  • Pobierz
  • Dodaj do moich podręczników
  • Drukuj
  • Strona
    / 110
  • Spis treści
  • BOOKMARKI
  • Oceniono. / 5. Na podstawie oceny klientów
Przeglądanie stron 47
30 Brsocade Adapters Troubleshooting Guide
53-1001253-01
FCoE and Fibre Channel problems
2
Adapter not registering with the name server or cannot access storage
If the adapter is not registering with the name server or cannot access storage, refer to the
following descriptions of possible causes and recommended actions to help solve the problem.
1. Possible Cause: Adapter cannot log in to the name server.
Action: Display logical port statistics (refer to “Logical port statistics” on page 58 for details on
displaying these statistics). Check for increasing name server port login (NS PLOGI) error
rejects and unknown name server port login response (NS login unknown rsp). These errors
mean that the adapter most likely cannot log in to the name server.
2. Possible Cause: Adapter has a problem registering with the name server.
Action: Display logical port statistics (refer to “Logical port statistics” on page 58 for details on
displaying these statistics). Check for increasing errors of the following types. These indicate
that the adapter has a problem registering with the name server:
Name server register symbolic port name identifier (NS RSPN_ID) errors.
Name server register symbolic port name identifier response (NS RFT_ID rsp) errors.
Name server register symbolic port name identifier response rejects (NS RFT_ID rejects).
3. Possible Cause: Adapter has a problem querying the name server for available storage.
Action: Display logical port statistics (refer to “Logical port statistics” on page 58 for details on
displaying these statistics). Check for increasing name server get all port ID response (NS
GID_FT rsp), rejects (NS_GID FT rejects), or unknown responses (NS_GID FT unknown rsp).
This indicates that the adapter has a problem querying the name server for available storage.
FCoE link is down
The FCoE link is down between the CNA and switch.
1. Possible Cause: The FCoE link is not administratively enabled.
Action: Determine if the link is enabled by entering the BCU port --list command. If the port is
administratively disabled, the “port state” field will show Disabled.
Action: Enable the port by entering the BCU port --enable <port_id> command.
2. Possible Cause: The CEE is not enabled on the CNA
Action: Verify that the CEE status using the BCU port –list command is displayed as “CEE
Linkup”. If “Linkdown” or “Linkup” displays, refer to “CEE is not enabled” on page 32.
3. Possible Cause: The VLAN to which the FCoE switch front-end port belongs is not FCF-capable.
Action: Verify if VLAN on front-end port is FCF-capable using the appropriate Fabric OS
command on the attached switch. Refer to the Fabric-OS Command Reference Manual for
more information.
Action: Set the VLAN as FCF-capable using the appropriate Fabric OS commands on the
attached FCoE switch. Refer to the Fabric-OS Command Reference Manual for more
information.
Przeglądanie stron 47
1 2 ... 43 44 45 46 47 48 49 50 51 52 53 ... 109 110

Komentarze do niniejszej Instrukcji

Brak uwag