infoblox_uddi:nios_x_xaas
Differences
This shows you the differences between two versions of the page.
| Next revision | Previous revision | ||
| infoblox_uddi:nios_x_xaas [2026/01/21 07:44] – created bstafford | infoblox_uddi:nios_x_xaas [2026/03/12 10:27] (current) – [BGP] bstafford | ||
|---|---|---|---|
| Line 18: | Line 18: | ||
| ===== POP ===== | ===== POP ===== | ||
| Infoblox can spin up XaaS instance in any AWS/GCP POP other than China. | Infoblox can spin up XaaS instance in any AWS/GCP POP other than China. | ||
| + | |||
| + | Availability Zones - within the region you have selected, NIOS-X will be deployed in TWO (no more, no less) Availability Zones in that region. Infoblox does not publish which AZ. If the region has more than two AZ then two AZ will be picked automatically for the customer. Infoblox does not publish which AZ the compute is deployed in. However, if you download a PCAP file for the POP via the Infoblox Portal, then you will notice that the file names are something like ddiaas_tcpdump_eu-west-2a_< | ||
| ===== Dynamic Routing ===== | ===== Dynamic Routing ===== | ||
| * eBGP only. | * eBGP only. | ||
| Line 24: | Line 26: | ||
| Identity can be KeyID or FQDN or Email. This is because some vendors (e.g. Cisco ASA firewall) don't support KeyID. | Identity can be KeyID or FQDN or Email. This is because some vendors (e.g. Cisco ASA firewall) don't support KeyID. | ||
| ===== VPN ===== | ===== VPN ===== | ||
| + | * Policy based VPN not supported. Route based VPN only. | ||
| + | |||
| The first exchange for the Phase two will work as the PFS is only exchanged during the ' | The first exchange for the Phase two will work as the PFS is only exchanged during the ' | ||
| Line 44: | Line 48: | ||
| < | < | ||
| + | |||
| + | * NIOS-XaaS currently accepts up to 100 routes over BGP. | ||
| + | * NIOS-XaaS recognized BGP Path Prepending and will prefer shorter paths over longer paths when it gets the same route from multiple peers. | ||
| + | * NIOS-XaaS will not use ECMP when it gets the same route from multiple peers. It will maintain one path at any given time. It will choose based on Path length (shortest is preferred), MED Metric (lowest is preferred) and router ID (lowest is preferred). | ||
| + | * 2 byte AS numbers have a max vlue of | ||
| + | * [[https:// | ||
| + | * [[https:// | ||
| + | * 4 byte AS numbers have a max value of 4, | ||
| + | * [[https:// | ||
| + | * [[https:// | ||
| + | * [[https:// | ||
| + | |||
| + | BGP 4 Byte information [[https:// | ||
| ===== Locations ===== | ===== Locations ===== | ||
| Auto location selection of Service works based on the nearest active POP to the geometric center of all Access Locations. | Auto location selection of Service works based on the nearest active POP to the geometric center of all Access Locations. | ||
infoblox_uddi/nios_x_xaas.1768981473.txt.gz · Last modified: by bstafford
