HP 1606 FICON Administrator's Guide v6.4.0 (53-1001771-01, June 2010) - Page 74

Symptom, Probable cause and recommended action, Fabric Not Con d Properly, Cabling

Get HP 1606 PDF manuals and user guides View all HP 1606 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 74 highlights

5 Common FICON issues Symptom Symptom Symptom Path to a device does not come online Probable cause and recommended action Make sure binding or zoning does not prevent the connection. Validate the following with the data center's system programmer: • Correct switch addresses (not switch IDs) are used in Link statements. Remember that the switch address is the domain ID converted to hex and may have an offset. • The Switch ID, used in the CHPID statements, was defined with the correct switch address. • All addressing (LINK statements) uses 2-byte addressing on the channel if 2-byte addressing has been previously used on that channel. This is necessary even when the specified path is not cascaded. Packets are being dropped between two FICON units. Probable cause and recommended action When planning cable needs, the following criteria must be considered: • Distance considerations • Fiber Optics Sub Assembly (FOSA) type (SW or LW) • Cable specifications (SM or MM) • Patch Panel Connections between FOSA ports (link loss .3-5 dB per) • Maximum allowable link budget (dB) loss From a cabling point of view, the most important factor of a Fibre Channel link is the selection of the Fibre Optical Sub Assembly (FOSA) and matching cable type, to support the required distance. Both ends of the optical link must have the matching FOSA (SFP) types. Channel path with 2-byte addressing does not come online Probable cause and recommended action Ask the operator what CHPID he is attempting to bring online. In FICON environments, only the egress ports are defined in the IOCDS. The CHPID number of the channel appears in the node list, but only if the channel path has logged in. If the channel path will not come online, it may not have completed a Fibre Channel fabric login. If this is the case, you will have to rely on customer documentation to determine what switch port the channel is connected to. Next, ask the operator what type of error message they are getting. An IOS error message is reported when there is an error external to the host; an IEE error message indicates something is wrong internal to the host. Fabric Not Configured Properly • Make sure that the insistent domain ID is set and the domain IDs are unique for all switches in the fabric. • Make sure that the same binding method is used on all switches in the fabric. • Scroll through the node list and make sure there are no invalid attachments. • Make sure that the re-routing delay is turned off. Cabling Validate that cables are connected where intended. 62 FICON Administrator's Guide 53-1001771-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
62
FICON Administrator’s Guide
53-1001771-01
Common FICON issues
5
Symptom
Path to a device does not come online
Probable cause and recommended action
Make sure binding or zoning does not prevent the connection. Validate the following with the data
center's system programmer:
•
Correct switch addresses (not switch IDs) are used in Link statements. Remember that the
switch address is the domain ID converted to hex and may have an offset.
•
The Switch ID, used in the CHPID statements, was defined with the correct switch address.
•
All addressing (LINK statements) uses 2-byte addressing on the channel if 2-byte addressing
has been previously used on that channel. This is necessary even when the specified path is
not cascaded.
Symptom
Packets are being dropped between two FICON units.
Probable cause and recommended action
When planning cable needs, the following criteria must be considered:
• Distance considerations
• Fiber Optics Sub Assembly (FOSA) type (SW or LW)
• Cable specifications (SM or MM)
• Patch Panel Connections between FOSA ports (link loss .3-5 dB per)
• Maximum allowable link budget (dB) loss
From a cabling point of view, the most important factor of a Fibre Channel link is the selection of
the Fibre Optical Sub Assembly (FOSA) and matching cable type, to support the required distance.
Both ends of the optical link must have the matching FOSA (SFP) types.
Symptom
Channel path with 2-byte addressing does not come online
Probable cause and recommended action
Ask the operator what CHPID he is attempting to bring online. In FICON environments, only the
egress ports are defined in the IOCDS. The CHPID number of the channel appears in the node list,
but only if the channel path has logged in. If the channel path will not come online, it may not have
completed a Fibre Channel fabric login. If this is the case, you will have to rely on customer
documentation to determine what switch port the channel is connected to.
Next, ask the operator what type of error message they are getting. An IOS error message is
reported when there is an error external to the host; an IEE error message indicates something is
wrong internal to the host.
Fabric Not Configured Properly
•
Make sure that the insistent domain ID is set and the domain IDs are unique for all switches in
the fabric.
•
Make sure that the same binding method is used on all switches in the fabric.
•
Scroll through the node list and make sure there are no invalid attachments.
•
Make sure that the re-routing delay is turned off.
Cabling
Validate that cables are connected where intended.