User Tools

Site Tools


infoblox_uddi:nios_x_xaas

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Next revision
Previous revision
infoblox_uddi:nios_x_xaas [2026/01/21 07:44] – created bstaffordinfoblox_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_<serial> and ddiaas_tcpdump_eu-west-2b_<serial> which indicates where the AZ are located.
 ===== 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 'Create Child_SA' exchange this usually occurs during re-key hence we see the first time the phase two comes up with the PFS mismatch, as one of the traffic selector is used during the IKE_SA_Init, and IKE_AUTH exchange The first exchange for the Phase two will work as the PFS is only exchanged during the 'Create Child_SA' exchange this usually occurs during re-key hence we see the first time the phase two comes up with the PFS mismatch, as one of the traffic selector is used during the IKE_SA_Init, and IKE_AUTH exchange
  
Line 44: Line 48:
  
 <code>Network > Virtual routers > BGP > Peer Group > Peer > Multi Hop</code> <code>Network > Virtual routers > BGP > Peer Group > Peer > Multi Hop</code>
 +
 +  * 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://datatracker.ietf.org/doc/html/rfc4893|RFC 4893]] defines 2 byte AS numbers (0 - 65,535)
 +      * [[https://datatracker.ietf.org/doc/html/rfc6996|RFC 6996]] defines private range of 2 byte AS numbers (64,512 - 65,534 inclusive)
 +  * 4 byte AS numbers have a max value of 4,294,967,295
 +      * [[https://datatracker.ietf.org/doc/html/rfc4893|RFC 4893]] defines 4 byte AS numbers (0 - 4,294,967,295)
 +      * [[https://datatracker.ietf.org/doc/html/rfc6996|RFC 6996]] defines private range of 4 byte AS numbers (4,200,000,000 - 4,294,967,294 inclusive)
 +      * [[https://www.arin.net/resources/guide/asn/|ASN reserved by ARIN for private use]]
 +
 +BGP 4 Byte information [[https://sites.google.com/site/amitsciscozone/bgp/understanding-bgp-4-byte|here]].
 ===== 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