Aviatrix VNFs规格
许可
自带许可证 (BYOL) 产品需要有效许可证。您负责从 Aviatrix 购买和管理您自己的许可证。要购买软件许可证，联系人您的 Aviatrix 销售代表或合作伙伴。
支持
Aviatrix的支持适用于BYOL许可证。请联系您的Aviatrix销售代表或合作伙伴，购买许可证和支持合同。
Aviatrix Spoke Edge
| 2 Cores | 4 Cores | 8 Cores | 16 Cores | |
|---|---|---|---|---|
| Memory | 4 GB | 8 GB | 16 GB | 32 GB |
| Software Package | Standard | |||
| Virtual Data Interfaces Supported (Default/Max) | 3/3 | |||
| System Reserved Interfaces | eth0(WAN) eth1(LAN) eth2(MGMT-WAN) | |||
| Available License Type | BYOL | |||
| Access Methods | SSH (CLI) Controller GUI | |||
| Image Version | See Available Image Versions* | |||
| Restricted CLI Commands | None | |||
| Deployment Options | Single Redundant |
- Aviatrix 6.9 版本最多支持 3 个接口，并且需要额外的支持设备才能实现三层路由功能。这意味着，如果您选择 6.9 版本，则需要通过 DLG 连接额外的支持设备（例如路由器）才能连接到 CSP。使用 7.1 版本则无需此要求。7.1 版本支持最多 10 个接口的多虚拟连接，并在 WAN 接口上支持 BGP，以支持 CSP 专用电路的连接。此版本需要 7.1 控制器。
Aviatrix Transit Edge
| 2 Cores | 4 Cores | 8 Cores | 16 Cores | |
|---|---|---|---|---|
| Memory | 4 GB | 8 GB | 16 GB | 32 GB |
| Software Package | Standard | |||
| Virtual Data Interfaces Supported (Default/Max) | 10/10 | |||
| System Reserved Interfaces | eth0(WAN) eth1(LAN) eth2(MGMT-WAN) | |||
| Available License Type | BYOL | |||
| Access Methods | SSH (CLI) Controller GUI | |||
| Image Version | See Available Image Versions* | |||
| Restricted CLI Commands | None | |||
| Deployment Options | Single Redundant |
*此版本需要 7.1 控制器。
创建一个Aviatrix Edge 设备
创建 Aviatrix Spoke Edge Device 或 Aviatrix Transit Edge Device 时，请考虑以下特定于供应商的选项。
配置文件
-
Aviatrix Spoke Edge 设备需要一个引导配置文件（Aviatrix 的默认配置文件），该文件必须在 Aviatrix Edge Controller 门户中生成。生成的文件名为
cloudinit ZTP.txt。 -
两种类型的 Aviatrix Edge 设备都需要一个设备配置文件，其中包含许可证、启动配置、控制器 IP 地址和加密密钥。请将此文件上传到“设备配置文件”部分。
旧版本
Aviatrix 6.9 版本最多支持 3 个接口，并且需要额外的支持设备才能实现三层路由功能。这意味着，如果您选择 6.9 版本，则需要通过 DLG 连接额外的支持设备（例如路由器）才能连接到 CSP。使用 7.1 版本时，此要求已取消。7.1 版本支持最多 10 个接口的多个虚拟连接，并在 WAN 接口上支持 BGP，以支持 CSP 专用电路连接。此版本需要 7.1 控制器。
连接选项
Aviatrix Edge VNF 提供“连接类型”功能。此功能允许您选择是否包含来自 Equinix 的公网 IP 地址的虚拟接口。VNF 无需公网 IP 地址即可启动，此选项适用于虚拟设备需要与互联网隔离的情况。用户随后可以通过其私有网络或虚拟连接管理这些设备。
下表总结了选项以及两者之间的区别。
| With Equinix Public IP Address | Without Equinix Public IP Address | |
|---|---|---|
| Use Cases | This option comes with Public IP Addresses from Equinix and does not need additional Virtual Connection to manage the virtual device. | This option removes Equinix-assigned Public IP Address assignment and will isolate VNF from the Internet after the device creation. This option is suitable for a scenario where the device needs to be managed by software running in the Colo cage or via private virtual connection. |
| Internet Connectivity Type | Public IP Address from Equinix are assigned to the interface and accessible from the Internet. User can also connect Aviatrix device to a supporting device (e.g., another router VNF) which already has the Internet connectivity. | No public IP Address from Equinix is included. As a prerequisite, a supporting device (e.g. a router with Equinix Public IP Address) needs to be created first with a Device Link Group (DLG) created. An Aviatrix Edge device without an Equinix IP Address can then be connected to the DLG so that it can immediately connect to the Aviatrix Controller. |
| Access Control List | Create an Access Control List (ACL) to limit traffic to the VNF interface. | ACL option is not available. Additional compensating controls can be implemented for traffic from any private virtual connection. |
| Interface Mapping | Eth0 to Eth9 (10 interfaces in total) are available for Aviatrix Edge device with Equinix IP Address. Eth2 is exclusively reserved as the WAN interface where public IP Address is assigned. Eth0 to Eth1, Eth3 to Eth9 can be used to map to DLG. Eth0, Eth3 to Eth9 can be connected to the CSP or virtual connection. | Eth0 to Eth9 (10 interfaces in total) are available for Aviatrix Edge device without Equinix IP Address. Eth0 to Eth9 can be used to map to DLG. Eth0, Eth2 to Eth9 can be connected to the CSP or virtual connection. |
只有拥有Equinix公共 IP 地址才能上传 ACL 模板和额外的互联网带宽。
如果您选择“无 Equinix 公网 IP 地址”类型，则需要通过支持设备提供互联网连接，该支持设备需在 24 小时内通过设备链路组 (DLG) 连接到 Aviatrix Edge 设备。Aviatrix 生成的 cloudinit ZTP 文件仅在生成后 24 小时内有效。如果 Edge 设备由于互联网不可用而在 24 小时内无法连接到 Aviatrix 控制器，则需要重新生成 cloudinit ZTP 文件并重新创建设备。