HP Brocade 8/12c Brocade Fabric OS Troubleshooting and Diagnostics Guide v6.2. - Page 94

Gathering additional information, portShow [slot number/]<geport number&gt

Get HP Brocade 8/12c PDF manuals and user guides View all HP Brocade 8/12c manuals
Add to My Manuals
Save this manual to your list of manuals

Page 94 highlights

10 FCIP links • IP addresses are retained by slot in the system. If FR4-18i blades are moved to different slots without first deleting configurations, errors can be seen when trying to reuse these IP addresses. • The portCmd --ping command only verifies physical connectivity. This command does not verify that you have configured the ports correctly for FCIP tunnels. • One port can be included in multiple tunnels, but each tunnel must have at least one port that is unique to that tunnel. • Ports at both ends of the tunnel must be configured correctly for an FCIP tunnel to work correctly. These ports can be either VE_Ports or VEX_Ports. A VEX_Port must be connected to a VE_Port. • When configuring routing over an FCIP link for a fabric, the edge fabric will use VE_Ports and the backbone fabric will use VEX_Ports for a single tunnel. • If an FCIP tunnel fails with the "Disabled (Fabric ID Oversubscribed)" message, the solution is to reconfigure the VEX_Port to the same Fabric ID as all of the other ports connecting to the edge fabric. • Because of an IPsec RASLog limitation, you may not be able to determine an incorrect configuration that causes an IPSec tunnel to not become active. This misconfiguration can occur on either end of the tunnel. As a result, you must correctly match the encryption method, authentication algorithm, and other configurations on each end of the tunnel. Gathering additional information The following commands should be executed and their data collected before a supportsave is run as a supportsave can take upwards of 10 minutes to execute and some of the information is time critical. • traceDump -n • portTrace --show all • portTrace --status In addition if it is a port/tunnel specific issue, run and collect the data from the following commands: • slotShow • portShow [slot number/] If possible, run and collect the data from the following commands: • portShow ipif [slot number/] Displays IP interface configuration for each GbE port (IP address, gateway and MTU) • portShow arp [slot number/] • portShow iproute [slot number/] • portShow fciptunnel [slot number/] Displays complete configuration of one or all of the FCIP tunnels • portShow fciptunnel -all -params • portShow fciptunnel -all -perf • portShow fciptunnel -all -credits • portCmd 78 Fabric OS Troubleshooting and Diagnostics Guide 53-1001187-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
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
78
Fabric OS Troubleshooting and Diagnostics Guide
53-1001187-01
FCIP links
10
•
IP addresses are retained by slot in the system. If FR4-18i blades are moved to different slots
without first deleting configurations, errors can be seen when trying to reuse these IP
addresses.
•
The
portCmd
--
ping
command only verifies physical connectivity. This command does not
verify that you have configured the ports correctly for FCIP tunnels.
•
One port can be included in multiple tunnels, but each tunnel must have at least one port that
is unique to that tunnel.
•
Ports at both ends of the tunnel must be configured correctly for an FCIP tunnel to work
correctly. These ports can be either VE_Ports or VEX_Ports. A VEX_Port must be connected to a
VE_Port.
•
When configuring routing over an FCIP link for a fabric, the edge fabric will use VE_Ports and
the backbone fabric will use VEX_Ports for a single tunnel.
•
If an FCIP tunnel fails with the “Disabled (Fabric ID Oversubscribed)” message, the solution is
to reconfigure the VEX_Port to the same Fabric ID as all of the other ports connecting to the
edge fabric.
•
Because of an IPsec RASLog limitation, you may not be able to determine an incorrect
configuration that causes an IPSec tunnel to not become active. This misconfiguration can
occur on either end of the tunnel. As a result, you must correctly match the encryption method,
authentication algorithm, and other configurations on each end of the tunnel.
Gathering additional information
The following commands should be executed and their data collected before a supportsave is run
as a supportsave can take upwards of 10 minutes to execute and some of the information is time
critical.
•
traceDump -n
•
portTrace --show all
•
portTrace --status
In addition if it is a port/tunnel specific issue, run and collect the data from the following
commands:
•
slotShow
•
portShow [slot number/]<geport number>
If possible, run and collect the data from the following commands:
•
portShow ipif [slot number/]<geport number>
Displays IP interface configuration for each GbE port (IP address, gateway and MTU)
•
portShow arp [slot number/]<geport number>
•
portShow iproute [slot number/]<geport number>
•
portShow fciptunnel [slot number/]<geport number> <all | tunnel ID>
Displays complete configuration of one or all of the FCIP tunnels
•
portShow fciptunnel -all -params
•
portShow fciptunnel -all -perf
•
portShow fciptunnel -all -credits
•
portCmd <--ping |--traceroute |--perf >