HP 6125G HP 6125G & 6125G/XG Blade Switches Layer 3 - IP Services Conf - Page 150

Configuring an IPv4 over IPv6 tunnel, Configuration prerequisites, Configuration guidelines

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

Page 150 highlights

Encapsulation is TUNNEL, service-loopback-group ID is 1. Tunnel source 3.1.1.1(Vlan-interface101), destination 2.1.1.1 Tunnel bandwidth 64 (kbps) Tunnel protocol/transport IP/IP Last 300 seconds input: 0 bytes/sec, 0 packets/sec Last 300 seconds output: 0 bytes/sec, 0 packets/sec 5 packets input, 320 bytes 0 input error 9 packets output, 576 bytes 0 output error # Ping the IPv4 address of the peer interface VLAN-interface 100 from Switch A. [SwitchA] ping 10.1.3.1 PING 10.1.3.1: 56 data bytes, press CTRL_C to break Reply from 10.1.3.1: bytes=56 Sequence=1 ttl=255 time=15 ms Reply from 10.1.3.1: bytes=56 Sequence=2 ttl=255 time=15 ms Reply from 10.1.3.1: bytes=56 Sequence=3 ttl=255 time=16 ms Reply from 10.1.3.1: bytes=56 Sequence=4 ttl=255 time=16 ms Reply from 10.1.3.1: bytes=56 Sequence=5 ttl=255 time=15 ms --- 10.1.3.1 ping statistics --5 packet(s) transmitted 5 packet(s) received 0.00% packet loss round-trip min/avg/max = 15/15/16 ms Configuring an IPv4 over IPv6 tunnel Configuration prerequisites Configure IP addresses for interfaces (such as the VLAN interface, and loopback interface) on the device to ensure normal communication. One of the interfaces will be used as the source interface of the tunnel. Configuration guidelines Follow these guidelines when you configure an IPv4 over IPv6 tunnel: • Specify public addresses or interfaces as the source end destination addresses or interfaces. • To encapsulate and forward IPv4 packets whose destination address does not belong to the subnet where the receiving tunnel interface resides, configure a static route or dynamic routing for forwarding those packets through this tunnel interface. If you configure a static route to that destination IPv4 address, specify this tunnel interface as the outbound interface, or the peer tunnel interface address as the next hop. A similar configuration is required at the other tunnel end. If you configure dynamic routing at both ends, enable the dynamic routing protocol on both tunnel interfaces. For the detailed configuration, see Layer 3-IP Routing Configuration Guide. • Two or more tunnel interfaces using the same encapsulation protocol must have different source and destination addresses. • If you specify a source interface instead of a source address for the tunnel, the source address of the tunnel is the primary IP address of the source interface. 142

  • 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
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
142
Encapsulation is TUNNEL, service-loopback-group ID is 1.
Tunnel source 3.1.1.1(Vlan-interface101), destination 2.1.1.1
Tunnel bandwidth 64 (kbps)
Tunnel protocol/transport IP/IP
Last 300 seconds input:
0 bytes/sec, 0 packets/sec
Last 300 seconds output:
0 bytes/sec, 0 packets/sec
5 packets input,
320 bytes
0 input error
9 packets output,
576 bytes
0 output error
# Ping the IPv4 address of the peer interface VLAN-interface 100 from Switch A.
[SwitchA] ping 10.1.3.1
PING 10.1.3.1: 56
data bytes, press CTRL_C to break
Reply from 10.1.3.1: bytes=56 Sequence=1 ttl=255 time=15 ms
Reply from 10.1.3.1: bytes=56 Sequence=2 ttl=255 time=15 ms
Reply from 10.1.3.1: bytes=56 Sequence=3 ttl=255 time=16 ms
Reply from 10.1.3.1: bytes=56 Sequence=4 ttl=255 time=16 ms
Reply from 10.1.3.1: bytes=56 Sequence=5 ttl=255 time=15 ms
--- 10.1.3.1 ping statistics ---
5 packet(s) transmitted
5 packet(s) received
0.00% packet loss
round-trip min/avg/max = 15/15/16 ms
Configuring an IPv4 over IPv6 tunnel
Configuration prerequisites
Configure IP addresses for interfaces (such as the VLAN interface, and loopback interface) on the device
to ensure normal communication. One of the interfaces will be used as the source interface of the tunnel.
Configuration guidelines
Follow these guidelines when you configure an IPv4 over IPv6 tunnel:
•
Specify public addresses or interfaces as the source end destination addresses or interfaces.
•
To encapsulate and forward IPv4 packets whose destination address does not belong to the subnet
where the receiving tunnel interface resides, configure a static route or dynamic routing for
forwarding those packets through this tunnel interface. If you configure a static route to that
destination IPv4 address, specify this tunnel interface as the outbound interface, or the peer tunnel
interface address as the next hop. A similar configuration is required at the other tunnel end. If you
configure dynamic routing at both ends, enable the dynamic routing protocol on both tunnel
interfaces. For the detailed configuration, see
Layer 3—IP Routing Configuration Guide
.
•
Two or more tunnel interfaces using the same encapsulation protocol must have different source and
destination addresses.
•
If you specify a source interface instead of a source address for the tunnel, the source address of the
tunnel is the primary IP address of the source interface.