From: Tom Lijnse (Tom.Lijnse@globalknowledge.nl)
Date: Thu Sep 15 2005 - 06:40:32 GMT-3
Hi Curt,
The main thing you need remember about ISATAP is that it is a
Client-to-Router tunneling mechanism (not a Router-to-Router mechanism
like 6to4).
This means that on the lab it would be hard to test as it requires a
client to test with. In other words, if this would be on the lab it
would probably be an exercise where you simply look it up on the Doc-CD,
modify the config to match your topology and the given restrictions and
hope for the best.
Personally I think that because of this the chances of getting ISATAP on
the lab are fairly low, as the Router-to-Router tunneling techniques are
actually testable and therefore allow for exercises that are a lot more
fun (or devious depending on your inclination).
On the other hand, instead of trying to estimate the chances of
something being on the lab or not, the better approach is to simply try
to understand the technology. So let me try to give you a hand with
that. As it turns out it's rather hard to find a decent example for
ISATAP with both the client side configuration and the router side. The
only one that I could find is inside the following Networkers
presentation:
www.cisco.com/warp/public/732/Tech/ipv6/docs/ipv6deployment.pdf
I must admit though that I've never configured this myself yet, so I
can't be 100% sure that the example is correct.
I hope this will at least give you another push in the right direction.
Regards,
Tom Lijnse
CCIE #11031
Global Knowledge
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
Curt Girardin
Sent: woensdag 14 september 2005 19:04
To: ccielab@groupstudy.com
Subject: FW: IPv6 ISATAP Tunnels
Hi,
Thanks for your input, I haven't yet understood it well-enough to
configure it yet. My lab workbooks have lots of IPv6 in it, so it's
only a matter of time before I will NEED to know it. Understanding that
it's really designed for dual-stack end-hosts helps a lot.
Thanks,
Curt
-----Original Message-----
From: Chris Lewis (chrlewis) [mailto:chrlewis@cisco.com]
Sent: Wednesday, September 14, 2005 9:32 AM
To: Curt Girardin; ccielab@groupstudy.com
Subject: RE: IPv6 ISATAP Tunnels
ISATAP is for dual stack hosts, ISATAP has a 64 bit IPv6 prefix and a 64
bit host portion created in EUI format. It is intended for v6 transport
over a
v4 infrastrucutre, so the routers adjacent to the v6 hosts do the
encapsulation/decapsulation of v6 packets in to v4 tunnels.
Intermediate routers do not need to be configured with ISATAP With
ISATAP you have to re-enable v6 router advertisements on the tunnel
interface to allow for client auto-configuration for handling multiple
hosts.
Have you tried to configure this and had problems?
Chris
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
Curt Girardin
Sent: Monday, September 12, 2005 8:33 PM
To: ccielab@groupstudy.com
Subject: IPv6 ISATAP Tunnels
Hi,
I'm having a really difficult time understanding ipv6 ISATAP tunnels;
although I understand IPv6 manual tunnels, IPv6 GRE tunnels, and Ipv6
6-to-4 auto tunnels.
I've read and re-read the cisco documentation and it seems very
high-level:
Few details on who is supposed to do encapsulation/decapsulation at each
end.
No details on how that embedded IPv4 address is used. Is this the next
hop?
A tunnel endpoint? Do all routers in-between also need to be configured
for ISATAP?
If the embedded IPv4 address is a tunnel endpoint, then how do you
handle multiple hosts at each site?
Is this really designed for dual-stack end-hosts?
Am I making this more complicated than it needs to be? I've also read
the IETF draft, and that's not much help either.
If anyone has a better explanation of this type of tunnel (along with
ipv4-compatable), I would very much appreciate it.
Here is the documentation I've read thus far:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios123/123cgcr/
ipv6_c/sa_tunv6.htm
http://www.ietf.org/internet-drafts/draft-ietf-ngtrans-isatap-24.txt
Thank you,
Curt
This archive was generated by hypermail 2.1.4 : Sun Oct 02 2005 - 14:40:15 GMT-3