Am working of MS UAG DirectAccess and we have 6 sites out there.
The requirement was to also have manage-out functionality working.
To get this done we have 1 global ISATAP cloud. In each Datacenter we have a Cisco 2800 running 6to4 tunneling and ISATAP tunnel for autoconfiguration of the hosts.
Now all is working with the default commands.
The challenge is that because we have 6 ISATAP routers the Win7 clients ISATAP adapter also has 6 default gateways in the local routing table. So it can happen that the traffic from a host is send half across the globe before reaching a ISATAP router.
Althought this router will then be able to send back the client to the correct ISATAP border router it's adding a huge delay.
Now I have a ISATAP tunnel on one of the boxes that looks like this.
interface Tunnel0 no ip address ipv6 address 2002:B1A1:6951:8000::/64 eui-64 ipv6 enable ipv6 nd prefix 2002:B1A1:695A:8100::/64 infinite infinite no-autoconfig no ipv6 nd suppress-ra tunnel source GigabitEthernet0/1 tunnel mode ipv6ip isatap end
I found that I can add several prefixes but this leads to having several IPs on the NIC of the ISATAP host.
Since this is one cloud, could you use an Anycast address for the ISATAP routers? This way, the hosts would see the same prefix from all ISATAP routers and configure only a single IPv6 address and should reach the 'closest' ISATAP router (based on routing metrics) due to the Anycast addressing.
Well the problem is not that they do not have an ip in the same cloud. They do. All ISATAP routers have the same IPv6 prefix setup and the clients get this prefix.
The problem is that because there are 6 isatap entries in DNS they connect to each one and get the info from all routers. This leads to 6 default ::/0 gateways. One towards each datacenter ISATAP router.
This means that a ISATAP client in SiteA could connect to ISATAP router in SiteB when it actually should talk to the SiteA ISATAP router.
In itself not a problem as the router in siteB have the correct routes so traffic is send back to the router in SiteA. But this leads to traffic flowing across the globe.
To resolve this I want to add routes to the advertisement so that the ISATAP router in SiteA adds a router to the local IPv6 nets connected to it.
Adding the second prefix as shows above works but the only thing is that the gateway for this router shows as On-Link. It should show the fe80:
Was hoping that anyone would know how to configure the ISATAP nd advertisement to make that happen. Or show me an alternative way of injecting a route into the WIN7 client routing table from an Cisco router.
or the IPv4 anycast you're probably using for your 6to4 relay: 22.214.171.124.
The clients would see only 1 IPv6 prefix, only "1" ISATAP router (the anycast address) and thus configure only 1 gateway route. Routing metrics would route the clients to the 'closest' ISATAP router, not across the globe. See:
We have 3 identical switches configured by someone else and would like to claim some of the Gigabit ports(G1/G2/G3/G4) for use on servers. When we try to change the wiring and configuration, we run in to connectivity issues. Attached is a des...
This is actually a pretty cool feature, i didn't even know it existed until I was looking for a solution to advertise a subnet (prefix in BGP talk), only if a certain condition existed. This is exactly what conditional advertisements does
j ai une question j ai achete un routeur cisco 887VA-k9 , je le configuré avec la configuration ci- dessous
si je le lier avec mon pc portable sur l un de ses ports directement ça marche toute est bien ( la connexion internet + m...