IPv6 ISATAP configuration example with a Cisco router as a client - Revision history

Pzimmerm: Added metadata template

2011-06-14T23:42:06Z

Added metadata template

← Older revision		Revision as of 23:42, 14 June 2011
Line 1:		Line 1:
	{{Template:Required Metadata}}		{{Template:Required Metadata}}
		+	{{Template:Metadata IPv6 Config Example}}

	==Introduction==		==Introduction==

2010-11-10T22:02:54Z

← Older revision		Revision as of 22:02, 10 November 2010
Line 18:		Line 18:
	==Configuration==		==Configuration==

-	'''Head-end router configuration'''	+	==='''Head-end router configuration'''===

	ipv6 unicast-routing		ipv6 unicast-routing
Line 33:		Line 33:
	tunnel mode ipv6ip isatap		tunnel mode ipv6ip isatap

-	'''Simulated ISATAP client on Cisco router'''	+	==='''Simulated ISATAP client on Cisco router'''===

	interface ethernet0		interface ethernet0

2010-11-10T21:48:29Z

Show running-config

← Older revision		Revision as of 21:48, 10 November 2010
Line 100:		Line 100:
	Head-end should be able to ping the client.		Head-end should be able to ping the client.
	router#ping ipv6 2001:DB8:CAFE:65::F02:880		router#ping ipv6 2001:DB8:CAFE:65::F02:880
-
	Type escape sequence to abort.		Type escape sequence to abort.
	Sending 5, 100-byte ICMP Echos to 2001:DB8:CAFE:65::F02:880, timeout is 2 seconds:		Sending 5, 100-byte ICMP Echos to 2001:DB8:CAFE:65::F02:880, timeout is 2 seconds:

2010-11-10T21:46:28Z

← Older revision		Revision as of 21:46, 10 November 2010
Line 89:		Line 89:
	O - OSPF Intra, OI - OSPF Inter, OE1 - OSPF ext 1, OE2 - OSPF ext 2		O - OSPF Intra, OI - OSPF Inter, OE1 - OSPF ext 1, OE2 - OSPF ext 2
	ON1 - OSPF NSSA ext 1, ON2 - OSPF NSSA ext 2		ON1 - OSPF NSSA ext 1, ON2 - OSPF NSSA ext 2
-	'''S ::/0 [2/0]	+	'''S ::/0 [2/0]'''
-	via FE80::5EFE:F64:801, Tunnel1'''	+	'''via FE80::5EFE:F64:801, Tunnel1'''
	C 2001:DB8:CAFE:65::/64 [0/0]		C 2001:DB8:CAFE:65::/64 [0/0]
	via Tunnel1, directly connected		via Tunnel1, directly connected

2010-11-10T21:44:49Z

Show running-config

← Older revision		Revision as of 21:44, 10 November 2010
Line 58:		Line 58:
	Client Tunnel1 should acquire IPv6 address prefix from head-end.		Client Tunnel1 should acquire IPv6 address prefix from head-end.
	Then client source IPv4 address is appended at the end.		Then client source IPv4 address is appended at the end.
-	In this ~~exampls~~, 15.2.8.128 => F02:880	+	In this example, 15.2.8.128 => F02:880

	'''show ipv6 interface tunnel1'''		'''show ipv6 interface tunnel1'''
Line 105:		Line 105:
	!!!!!		!!!!!
	Success rate is 100 percent (5/5), round-trip min/avg/max = 0/0/0 ms		Success rate is 100 percent (5/5), round-trip min/avg/max = 0/0/0 ms
-

	==Related Information==		==Related Information==

2010-11-10T21:42:08Z

← Older revision		Revision as of 21:42, 10 November 2010
Line 57:		Line 57:
	==Show running-config==		==Show running-config==
	Client Tunnel1 should acquire IPv6 address prefix from head-end.		Client Tunnel1 should acquire IPv6 address prefix from head-end.
-	Then ~~it appends~~ client source IPv4 address ~~to then~~ end.	+	Then client source IPv4 address is appended at the end.
	In this exampls, 15.2.8.128 => F02:880		In this exampls, 15.2.8.128 => F02:880

2010-11-10T20:14:30Z

← Older revision		Revision as of 20:14, 10 November 2010
Line 3:		Line 3:
	==Introduction==		==Introduction==

-	This example demonstrates ISATAP configuration on the head-end router and a simulated ISATAP client using a Cisco router.	+	This example demonstrates ISATAP configuration on the head-end router and a simulated ISATAP client using a Cisco router.<br>
	Usually the client is a Windows PC with IPv6 enabled, initiating the tunnel.		Usually the client is a Windows PC with IPv6 enabled, initiating the tunnel.
-	For testing and verification purposes, a Cisco router closest to the clients can act as a client.	+	For testing and verification purposes, a Cisco router closest to the clients can act as a client.<br>
	For this, we are using ISATAP tunnel at the head-end and IPv6 over IPv4 manual tunnel at the client router.		For this, we are using ISATAP tunnel at the head-end and IPv6 over IPv4 manual tunnel at the client router.
-	Check feature navigator to verify head-end router image supports ISATAP tunnels.	+	IPv6 unicast routing can be disabled on the client router, so that it will behave as a true client and install a default IPv6 static route towards the head-end.<br>
		+	Check feature navigator to verify head-end router image supports ISATAP tunnels.<br>
	Check feature navigator to verify simulated client router supports manually configured IPv6 over IPv4 tunnels.		Check feature navigator to verify simulated client router supports manually configured IPv6 over IPv4 tunnels.

2010-11-10T19:51:55Z

← Older revision		Revision as of 19:51, 10 November 2010
Line 112:		Line 112:

	<!--Add appropriate categories-->		<!--Add appropriate categories-->
		+	[[Category: IPv6 Configuration Examples]]

2010-11-10T19:40:41Z

← Older revision		Revision as of 19:40, 10 November 2010
Line 6:		Line 6:
	Usually the client is a Windows PC with IPv6 enabled, initiating the tunnel.		Usually the client is a Windows PC with IPv6 enabled, initiating the tunnel.
	For testing and verification purposes, a Cisco router closest to the clients can act as a client.		For testing and verification purposes, a Cisco router closest to the clients can act as a client.
		+	For this, we are using ISATAP tunnel at the head-end and IPv6 over IPv4 manual tunnel at the client router.
	Check feature navigator to verify head-end router image supports ISATAP tunnels.		Check feature navigator to verify head-end router image supports ISATAP tunnels.
	Check feature navigator to verify simulated client router supports manually configured IPv6 over IPv4 tunnels.		Check feature navigator to verify simulated client router supports manually configured IPv6 over IPv4 tunnels.

2010-11-10T19:29:37Z

← Older revision		Revision as of 19:29, 10 November 2010
Line 96:		Line 96:
	via Null0, receive		via Null0, receive

		+	Head-end should be able to ping the client.
		+	router#ping ipv6 2001:DB8:CAFE:65::F02:880
		+
		+	Type escape sequence to abort.
		+	Sending 5, 100-byte ICMP Echos to 2001:DB8:CAFE:65::F02:880, timeout is 2 seconds:
		+	!!!!!
		+	Success rate is 100 percent (5/5), round-trip min/avg/max = 0/0/0 ms