Meant to be used in conjunction with SDNExpress, SCVMM Deployments, or for do-it-yourself deployments.
Update-SDNExpressDNSZonePermissions - Gives the network controller computer objects the required permissions on the DNS zone to be able to update the REST DNS name when the service fabric replica for the API moves to another node. Needs to be ran per Network Controller, requires AD RSAT PowerShell module to be installed, and the credentials need rights to modify the DNS application partition in Active Directory.
Update-SDNExpressMuxRoutes - Does two things
- Creates a static route on the Mux that directs traffic destined for remote HNVPA networks, like nodes under another top of rack switch, in the same SDN stamp, out via the HNVPA network adapter. This way VXLAN is encapsulated using an adapter that has the encapoverhead property set. If you only have one top of rack switch pair, this section does nothing.
- Creates a static route to the top of rack switch BGP peering IP address using the next hop of the supplied front end router, via the following interface: transit, in the case of a 3 nic SLB MUX, or the dual purpose HNVPA adapter in the case of a 2 nic SLB Mux. This is important for BGP peering because the top of rack switch generally has EBGP MULTIHOP set to a value of 2 or 3, and attempting to peer from another interface might increase the hop count past that limit. This needs to be ran per SLB Mux
SDN High Level v2.1.pdf - this is an infographic that trys to convey in graphic form, the required switch configuration for running multiple Azure Stack HCI clusters, under multiple top of rack switches, under the same SDN deployment.