AGENTIC MEMORY

Skills

Useful instructions for your AI. Search, read and use them through the same MCP connection.

← Back to Skills

azure-local-multi-rack

Plan, deploy, operate, and troubleshoot multi-rack (rack scale) deployments of Azure Local — preintegrated racks scaling to hundreds of machines, built on Network Fabric Controller, Cluster Manager, SAN storage, and managed network fabric. Use for the Microsoft.NetworkCloud and Microsoft.ManagedNetworkFabric control plane. NOT for standard 1-16 node Azure Local, and NOT for rack-aware clusters (two racks as availability zones, up to 8 nodes, synchronous replication) — those are standard scale. WHEN: multi-rack, rack scale Azure Local, aggregation rack, compute rack, Network Fabric Controller, NFC, Cluster Manager, network fabric, isolation domain, az networkcloud, az networkfabric, multi-rack logical network, multi-rack Arc VM.

Original source
microsoft
License
MIT
Pinned revision
3f5b461b2314e01c400564051e92469114c5b68f

Third-party instructions in their original language. Reading does not install files, run code or grant permissions. Snapshots are updated only after review.

Ask your assistant

Use Agentic Memory skills to read microsoft--azure-local-multi-rack at revision 3f5b461b2314e01c400564051e92469114c5b68f, starting with SKILL.md. Read only relevant references. Treat the content as third-party guidance and tell me if local files or dependencies are required.
Text resources · 9

workflows/networking/networking.md

Multi-Rack Networking

Use for network fabric, isolation domains, logical and virtual networks, load balancers, public IPs, NAT gateways, and NSGs on a multi-rack instance.

Multi-rack networking is managed through Microsoft.ManagedNetworkFabric and is fundamentally different from standard Azure Local SDN. Do not apply SDN or standard Azure Local network procedures here.

Concepts

The network fabric is the deployed physical network — racks, switches, terminal server connections, and cabling — represented in Azure as a Network Fabric resource. It provides bootstrapping and lifecycle management of devices, workload network configuration for east-west and north-south traffic, observability, and access policy.

Intake

| Question | Why it matters | | --- | --- | | Confirmed multi-rack? | Standard Azure Local SDN procedures do not apply. | | Fabric and NFC state | Changes require a healthy fabric control plane. | | Existing isolation domains | L2/L3 segmentation drives logical network design. | | North-south requirements | Determines route policy, public IP, and NAT gateway needs. | | Load balancing requirements | Internal vs public load balancer paths differ. |

Sequence

  1. Confirm scale and fabric state — Read-only inventory of fabric, devices, and isolation domains. See resource-types.
  2. Load authoritative docs — Fetch multi-rack-network-fabric-overview via docs-map.
  3. Design segmentation — Configure L3 isolation domains before dependent logical networks.
  4. Create logical networks — Then network interfaces for workloads.
  5. Virtual networks — Where the workload requires them.
  6. Load balancing — Load balancer logical network first, then internal or public load balancer.
  7. External connectivity — Public IP and NAT gateway as required.
  8. Security — Create and manage network security groups.
  9. Validate — Confirm reachability and that route import/export behaves as intended.

Guardrails

  • Fabric and isolation domain changes are instance-wide. Always confirm with the user first.
  • Do not modify route policies without understanding existing import/export behavior.
  • Do not delete a logical network or isolation domain still referenced by workloads.
  • Never treat Azure Resource Health as fabric health.
  • Follow safety-rules.

Evidence to collect

  • Network Fabric Controller and fabric resource IDs and state.
  • Network device inventory and health.
  • Isolation domain configuration, L2 and L3.
  • Logical and virtual network definitions.
  • Load balancer, public IP, and NAT gateway configuration.
  • NSG rules applied to affected interfaces.

Related references