HP 1606 Fabric OS FCIP Administrators Guide v6.4.0 (53-1001766-01, November 20 - Page 38

Support for IPv6 Addressing

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 38 highlights

2 Support for IPv6 Addressing FIGURE 9 Multiple tunnels to multiple ports, Fastwrite and OSTP enabled on a per-tunnel/per-port basis In some cases, traffic isolation zoning TI or LS/LF configurations may be used to control the routing of SID/DID pairs to individual tunnels and provide deterministic flows between the switches, allowing the use of multiple equal cost tunnels. Refer to the Fabric OS Administrator's Guide for more information about traffic isolation zoning. Support for IPv6 Addressing The IPv6 implementation is a Dual IP Layer Operation implementation as described in RFC 4213. IPv6 addresses can exist with IPv4 addresses on the same interface, but the FCIP circuits configured must be as IPv6 to IPv6 and IPv4 to IPv4 connections. IPv6 to IPv4 connections are not supported. Likewise, encapsulation of IPv4 in IPv6 and IPv6 in IPv4 is not supported. This implementation of IPv6 uses unicast addresses for the interfaces with FCIP circuits. Unicast address must follow the RFC 4291 IPv6 standard. This IPv6 implementation uses the IANA assigned IPv6 Global Unicast address space (2000::/3). The starting three bits must be 001 (binary) unless IPV6 with embedded IPv4 addresses is used. The link-local unicast address is automatically be configured on the interface, but using the link-local address space for FCIP circuit end points is not allowed. Site-local unicast addresses are not be allowed as FCIP circuit end points. • Anycast addresses will not be used. Each IPv6 interface will have a unique unicast address and addresses configured are assumed to be unicast. • Multicast addresses cannot be configured for an IPv6 interface with FCIP circuits. The IPv6 interface will not belong to any Multicast groups other than the All-Nodes Multicast and the Solicited-Node Multicast (these do not require user configuration). • The IPv6 implementation will follow the RFC 2460 standard for the 40 bit fixed IPv6 header format. 24 Fabric OS FCIP Administrator's Guide 53-1001766-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
24
Fabric OS FCIP Administrator’s Guide
53-1001766-01
Support for IPv6 Addressing
2
FIGURE 9
Multiple tunnels to multiple ports, Fastwrite and OSTP enabled on a per-tunnel/per-port basis
In some cases, traffic isolation zoning TI or LS/LF configurations may be used to control the routing
of SID/DID pairs to individual tunnels and provide deterministic flows between the switches,
allowing the use of multiple equal cost tunnels. Refer to the
Fabric OS Administrator’s Guide
for
more information about traffic isolation zoning.
Support for IPv6 Addressing
The IPv6 implementation is a Dual IP Layer Operation implementation as described in RFC 4213.
IPv6 addresses can exist with IPv4 addresses on the same interface, but the FCIP circuits
configured must be as IPv6 to IPv6 and IPv4 to IPv4 connections. IPv6 to IPv4 connections are not
supported. Likewise, encapsulation of IPv4 in IPv6 and IPv6 in IPv4 is not supported.
This implementation of IPv6 uses unicast addresses for the interfaces with FCIP circuits. Unicast
address must follow the RFC 4291 IPv6 standard. This IPv6 implementation uses the IANA
assigned IPv6 Global Unicast address space (2000::/3). The starting three bits must be 001
(binary) unless IPV6 with embedded IPv4 addresses is used. The link-local unicast address is
automatically be configured on the interface, but using the link-local address space for FCIP circuit
end points is not allowed. Site-local unicast addresses are not be allowed as FCIP circuit end
points.
•
Anycast addresses will not be used. Each IPv6 interface will have a unique unicast address and
addresses configured are assumed to be unicast.
•
Multicast addresses cannot be configured for an IPv6 interface with FCIP circuits. The IPv6
interface will not belong to any Multicast groups other than the All-Nodes Multicast and the
Solicited-Node Multicast (these do not require user configuration).
•
The IPv6 implementation will follow the RFC 2460 standard for the 40 bit fixed IPv6 header
format.