virtualization:cloud:azure
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| virtualization:cloud:azure [2025/01/14 14:53] – jotasandoku | virtualization:cloud:azure [2025/01/14 15:02] (current) – [Route Propagation] jotasandoku | ||
|---|---|---|---|
| Line 5: | Line 5: | ||
| * EXPRESS ROUTE | * EXPRESS ROUTE | ||
| * Azure Firewall | * Azure Firewall | ||
| - | * | + | * Virtual HUb (~AWS TGW) |
| * Cross VNET peering | * Cross VNET peering | ||
| * Azure virtual NAT | * Azure virtual NAT | ||
| Line 11: | Line 11: | ||
| * Azure Load Balancer | * Azure Load Balancer | ||
| * Traffic Manager | * Traffic Manager | ||
| - | * Azure Aplication | + | * Azure Application |
| - | * NVA in Virtual Hub | + | * NVA in Virtual Hub - see [[https:// |
| * Resource manager (is the infrastructure tool ~ cloud formation) | * Resource manager (is the infrastructure tool ~ cloud formation) | ||
| * Subscription (~account) | * Subscription (~account) | ||
| Line 19: | Line 19: | ||
| ---- | ---- | ||
| - | === Azuer specific concepts === | + | === Azure specific concepts === |
| - | * Management groups > Subscruptions | + | * Management groups > Subscriptions |
| * SKU (from the classical sku ) : Is the specific version or offering of a resource (vms, storage accounts, databases, | * SKU (from the classical sku ) : Is the specific version or offering of a resource (vms, storage accounts, databases, | ||
| Line 27: | Line 27: | ||
| ---- | ---- | ||
| ACTIVE DIRECTORY IN AZURE - named ENTRA ID : [[https:// | ACTIVE DIRECTORY IN AZURE - named ENTRA ID : [[https:// | ||
| - | \\ | ||
| - | ---- | ||
| - | ====== Azure Networking Overview (Webinar: 2021-04-08) | + | ===== Azure Networking Overview (Webinar: 2021-04-08) ===== |
| ===== General Notes ===== | ===== General Notes ===== | ||
| Line 39: | Line 37: | ||
| ===== Virtual Hubs ===== | ===== Virtual Hubs ===== | ||
| - | * Most Azure networking relies on **Virtual Hubs**. | + | * Most Azure **networking** relies on **Virtual Hubs**. |
| * A virtual hub is essentially a VNet implemented with a group of Windows servers performing routing functions. | * A virtual hub is essentially a VNet implemented with a group of Windows servers performing routing functions. | ||
| + | * [[https:// | ||
| * **Virtual WANs and Hubs**: | * **Virtual WANs and Hubs**: | ||
| * Traffic traversing virtual hubs incurs charges based on **time**, not traffic volume (to be confirmed). | * Traffic traversing virtual hubs incurs charges based on **time**, not traffic volume (to be confirmed). | ||
| Line 50: | Line 49: | ||
| * Command: `az network nic show-effective-route-table` | * Command: `az network nic show-effective-route-table` | ||
| * Example from Webinar (Slide 18): Shows route table for a NIC. | * Example from Webinar (Slide 18): Shows route table for a NIC. | ||
| - | * Query: Can this functionality be replicated in OCI? | ||
| ===== Route Propagation ===== | ===== Route Propagation ===== | ||
| * Virtual hubs propagate routes and manage connectivity automatically. | * Virtual hubs propagate routes and manage connectivity automatically. | ||
| * Unlike AWS Transit Gateway, which requires manual static route configuration. | * Unlike AWS Transit Gateway, which requires manual static route configuration. | ||
| - | * Query: How does OCI handle route propagation? | ||
| * **Labels** (similar to MPLS Route Targets) can control propagation between route tables (Slide 20). | * **Labels** (similar to MPLS Route Targets) can control propagation between route tables (Slide 20). | ||
| * **AS-Prepending** is the only way to influence route preferences (similar to OCI). | * **AS-Prepending** is the only way to influence route preferences (similar to OCI). | ||
virtualization/cloud/azure.1736866408.txt.gz · Last modified: by jotasandoku
Page Tools
Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Share Alike 4.0 International
