At a high level I think we need to:

• Create an aggregate policy on cloudsw1-b1-codfw to generate 2a02:ec80:a100::/48 if participating routes are present
• Allocate /64 subnets from 2a02:ec80:a100:fe00::/55 for link networks and vlans
  • cr1-codfw uplink - cloud vrf (.1001)
  • cr2-codfw uplink - cloud vrf (.1001)
  • vlan: cloud-instance-transport1-b-codfw (between cloudsw and cloudgw)
  • vlan: cloud-gw-transport-codfw (between cloudgw and cloudnet)
• Route 2a02:ec80:a100::/55 to the cloudgw VIP on cloud-instance-transport1-b-codfw

All of this happens within the 'cloud' vrf on the cloudsw.

here is a proposal:

• 2a02:ec80:a100:fe01::/64 - cr1-codfw uplink
• 2a02:ec80:a100:fe02::/64 - cr2-codfw uplink
• 2a02:ec80:a100:fe03::/64 - cloud-instance-transport1-b-codfw (between cloudsw and cloudgw)
• 2a02:ec80:a100:fe04::/64 - cloud-gw-transport-codfw (between cloudgw and cloudnet)

That seems fine to me @aborrero thanks!

Created:

• https://netbox.wikimedia.org/ipam/prefixes/1085/
• https://netbox.wikimedia.org/ipam/prefixes/1086/
• https://netbox.wikimedia.org/ipam/prefixes/1087/
• https://netbox.wikimedia.org/ipam/prefixes/1088/

In T374713#10199236, @aborrero wrote:

Created:

Thanks! I've made some minor edits to them in Netbox btw, just some things you probably won't be familiar with.

The two relating to vlans I set the associated vlan on the prefix (and removed the vlan name from the description field). On all 4 I removed the 'vrf' setting. Technically they are 100% in the cloud vrf, however the way we have VRFs automated we just set it on interfaces in Netbox, not on IP ranges. That way we don't partition our address space and Netbox still makes sure all addresses are unique across any VRF.