deepblue/windows-itpro-docs
1
0
Fork 0
mirror of https://github.com/MicrosoftDocs/windows-itpro-docs.git synced 2025-05-12 05:17:22 +00:00
Code Issues Actions 2 Packages Projects Releases Wiki Activity
windows-itpro-docs/windows/deployment/do/mcc-isp-configure-routing.md

2.1 KiB
Raw Blame History

Configure client routing for cache node

All configuration routing takes place within the Azure Portal. There are two main methods to route clients to your cache node:

  • Manual Routing: Providing the CIDR blocks that represent the client IP address space, which should be routed to the MCC node.
  • BGP Routing: BGP neighborship sessions from the cache node to the router or route server will be initiated automatically based on the portal configuration.

Note

Only IPv4 addresses are supported at this time. Entering IPv6 addresses will result in an error.

Manual Routing

  1. To configure client routing using manually entered CIDR blocks, navigate to Settings >> Routing Information.
  2. Select Manual prefix entry as the Prefix Source.
  3. Paste in the CIDR blocks, with each IP range separated by a comma.
  4. Lastly, press Save to save your changes.

BGP Routing

  1. To configure client routing using BGP, navigate to Settings >> Routing Information.
  2. Select BGP as the Prefix source.
  3. Click on Add neighbor to add the ASN(s) and IP address(es) of your BGP neighbors.
  4. If you'd like to download your BGP routes, click on the Download Routes button.
  5. Lastly, press Save to save your changes.
  6. From your end, establish a neighborship from your router to MCC's host machine. Use the IP address of the host machine that's running the MCC container.

Note

With the BGP configuration, you're essentially setting up an iBGP neighbor in your public ASN. For example, when you initiate the BGP session from the router to the cache node, you would use your own ASN.

a. Make sure there aren't any firewall rules blocking this connection. b. Verify that the BGP connection has been established and that you're advertising routes to the MCC. c. Wait five minutes to refresh the cache node page in the Azure portal to see the BGP routes.

  1. If there are errors: