HP StorageWorks 8/80 Brocade Troubleshooting and Diagnostics Guide v6.1.0 (53- - Page 86

Gathering additional information, Port mirroring

Get HP StorageWorks 8/80 - SAN Switch PDF manuals and user guides View all HP StorageWorks 8/80 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 86 highlights

9 Port mirroring • 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. • Due to 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 • portCmd Ping and traceroute utility Performance to determine path characteristics between FCIP endpoints And finally gather the data from the supportsave -n command. See Fabric OS Administrator's Guide or Fabric OS Command Reference for complete details on these commands Port mirroring Port mirroring lets you configure a switch port to connect to a port to mirror a specific source port and destination port traffic passing though any switch port. This is only supported between F_Ports. This is a useful way to troubleshoot without bringing down the host and destination links to insert an inline analyzer. 72 Fabric OS Troubleshooting and Diagnostics Guide 53-1000853-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
72
Fabric OS Troubleshooting and Diagnostics Guide
53-1000853-01
Port mirroring
9
•
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.
•
Due to 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
•
portCmd <--ping |--traceroute |--perf >
Ping and traceroute utility
Performance to determine path characteristics between FCIP endpoints
And finally gather the data from the supportsave -n command.
See
Fabric OS Administrator’s Guide
or
Fabric OS Command Reference
for complete details on
these commands
Port mirroring
Port mirroring lets you configure a switch port to connect to a port to mirror a specific source port
and destination port traffic passing though any switch port. This is only supported between F_Ports.
This is a useful way to troubleshoot without bringing down the host and destination links to insert
an inline analyzer.