For customers just hosting a single server, why don't you use a routed port? You can then do SLAAC or DHCPv6. The customer can use those or elect to use a static address from the /64. Since this is directly connected you don't need additional routing. You can summarize the /64s when you advertise routes to neighboring devices.
For customers that want their own router/firewall use a /64 for the link from your 7k to their CPE. Then assign them a /64 or /60 or whatever you arrange. For that I would use a static route to the CPE again making sure to summarize. For a small setup like your describing I wouldn't use an IGP. This doesn't fit with the customer type you're describing.
My impression of DHCP-PD is its more targeted for residential/SMB customers and not hosting environments.
I agree with you, the solution for the "one server" customer is the "connected" subnet, so no further entries are needed there.
The issue is in fact for the /64 backend subnets of the other customers. I think I was not clear before, the scenario is not a small setup, but we have thousands of these customers that are now attached to the same Router (in IPv4). The diagram is just an example, multiply the customers on the diagram by a 500 factor.
Let's consider 1500 customers. Today they are all in the same frontend subnet, "hiding" their backend subnets via IPv4 PAT.
Now we are migrating to IPv6 and we are giving 1500 /64 subnets that the customer can use on his backend.
The question is: what is the best way to reach there 1500 backend subnets?
Placing 1500 static routes might work, but it does not seem a very nice/elegant solution.
Moreover I wonder if a config file this large could give any kind of issue, or if the Nexus could suffer due to the number of IPv6 routes it would have to handle.
Listen: https://smarturl.it/CCRS8E37Follow us: twitter.com/ciscochampionSometimes, situations require temporary fixes. Sometimes, the network becomes an afterthought in overall office design and planning. In either situation, it may require netw...
In this special edition of the Insider Series, we hear from Cisco partners who have taken steps to be more eco-friendly and sustainable. We hear what inspires ASHRAE, Southwire, Igor, and NTT to create a workplace that is centered around people and how th...
We know that the Type-1 LSA describes the link type connected to the router, the neighbor router and the subnet number.In this topology, assume we dont have a Type-2 LSA, so each router will create its own Type-1 LSA, the Type-1 LSA will describe the neig...
Here are some commonly asked questions and answers to help with your adoption of Cisco DNA Center Wireless. Subscribe to this post to stay up-to-date with the latest Q&A and recommended Ask the Experts (ATXs) sessions to attend.
Q. I have a Cisco Appl...
Why IETF changed and inverted OSPF Type-7 LSA VS Type-5 LSA election In RFC 3101 compared to OLD RFC 1587?Many people learns that the Type-7 LSA and Type-5 election (ON Versus OE routes) depends on RFC 3101 for NSSA published in 2003 and RFC 1587 for NSSA...