HP StorageWorks 2/16V HP StorageWorks Fabric OS V3.1.3A Release Notes (AA-RUQY - Page 24

description. If two switches are specified back to back in the source route

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

Page 24 highlights

CLI Command Updates and Changes Source route The source route option allows the user to specify a sequence of switches or ports (or areas) that the pathInfo frame has to follow to reach the destination. Therefore, the path might be different from the one the actual traffic from source to destination will take. The source route is expressed as a sequence of switches, a sequence of output ports (or areas), or a combination thereof. The next hop in the source route is described by either the output port (or area) to be used to reach the hop or the domain ID of the next hop. The source route can specify a partial route from source to destination (in which case the remaining hops are chosen as the path from the input port (or area) on the first hop not listed in the source route to the destination), as a full route, or as an arbitrary route across the fabric. The maximum hop count is enforced. If the source route does not specify all the switches along a section of the path, a further option allows you to specify a strict path versus a loose path. A strict source route requires that only the specified switches are reported in the path description. If two switches are specified back to back in the source route descriptor but are not directly connected, the switches in between will be ignored. In the case of a loose source route, the switches in between will be reported. The concepts of strict and loose route apply to the portion(s) of the path described by domains, not to the part described by output ports/areas. Operands The following operands are allowed: domain The ID of the destination domain. source port The port (or area) whose path to the destination domain is sought. The embedded port (-1) is used by default. For a switch with blades, the destination is specified as the area; otherwise, as the port. If the source port is given as -1 with no additional arguments, then basic statistics will be displayed for the route. 24 Fabric OS 3.1.3a Release Notes

  • 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
CLI Command Updates and Changes
24
Fabric OS 3.1.3a Release Notes
Source route
The source route option allows the user to specify a sequence of switches or ports
(or areas) that the
pathInfo
frame has to follow to reach the destination.
Therefore, the path might be different from the one the actual traffic from source
to destination will take.
The source route is expressed as a sequence of switches, a sequence of output
ports (or areas), or a combination thereof. The next hop in the source route is
described by either the output port (or area) to be used to reach the hop or the
domain ID of the next hop.
The source route can specify a partial route from source to destination (in which
case the remaining hops are chosen as the path from the input port (or area) on the
first hop not listed in the source route to the destination), as a full route, or as an
arbitrary route across the fabric. The maximum hop count is enforced.
If the source route does not specify all the switches along a section of the path, a
further option allows you to specify a
strict path
versus a
loose path
. A strict
source route requires that only the specified switches are reported in the path
description. If two switches are specified back to back in the source route
descriptor but are not directly connected, the switches in between will be ignored.
In the case of a loose source route, the switches in between will be reported. The
concepts of strict and loose route apply to the portion(s) of the path described by
domains, not to the part described by output ports/areas.
Operands
The following operands are allowed:
domain
The ID of the destination domain.
source port
The port (or area) whose path to the destination
domain is sought. The embedded port (-1) is used
by default. For a switch with blades, the
destination is specified as the area; otherwise, as
the port. If the source port is given as -1 with no
additional arguments, then basic statistics will be
displayed for the route.