Palo Alto Networks – VM Series (Equinix-Configured)
|
|
CPU = 2 cores Memory = 8G Disk size = 80G |
CPU = 4 cores Memory = 16G Disk size = 80G |
CPU = 8 cores Memory = 48G Disk size = 80G |
CPU = 16 cores Memory = 56G Disk size = 80G |
|---|---|---|---|---|
| Software Package | VM 100 |
VM 100 |
VM 100 |
VM 100 VM 300 VM 500 VM 700 |
| Minimum Interfaces Supported (# data interfaces available) |
10 | 10 | 10 | 10 |
| Maximum Interfaces Supported (# data interfaces available) |
10 | 19 | 19* | 19 |
| Routing Domains |
MGMT |
MGMT |
MGMT |
MGMT External Cloud virtual routers |
| License Types Supported |
BYOL Subscription Authcode for provisioning and deprovisioning |
BYOL Subscription Authcode for provisioning and deprovisioning |
BYOL Subscription Authcode for provisioning and deprovisioning |
BYOL Subscription Authcode for provisioning and deprovisioning |
| Boot Time Average | 20 minutes | 20 minutes | 20 minutes | 20 minutes |
| BGP Local AS Support |
Yes | Yes | Yes | Yes |
| Access Methods |
HTTPS |
HTTPS |
HTTPS |
HTTPS Web UI |
| Image Version |
9.1.12 |
9.1.12 |
9.1.12 |
9.1.12 |
| Restricted CLI Commands | ||||
| Throughput | Throughput (IMIX): 1 Gbps: IP-BASE (cvim: 2.4.15, 3.4.3); 360 Mbps: IP-SEC (9.0.0, 9.0.1)1500B IP-Base: 4 Gbps (cvim: 2.4.15, 3.4.3); 1350B IP-SEC: 640 Mbps |
Throughput (IMIX): 2 Gbps: IP-BASE; 720 Mbps: IP-SEC1500B IP-Base: 6.4 Gbps; 1350B IP-SEC: 1.6 Gbps (9.0.1) | Throughput (IMIX): 5 Gbps: IP-BASE, 700 Mbps: IP-SEC (9.0.0), 1.5 Gbps: IP-SEC (9.0.1)1500B IP-Base: 12 Gbps, 1350B IP-SEC: 1.8 Gbps (9.0.0), 3.0 Gbps (9.0.1) |
|
| Vendor Product Specs |
https://www.paloaltonetworks.com/resources/datasheets/vm-series-specsheet | |||
|
Services Offered
|
|
|||
| Other Notes | Loopback interface – yes | Loopback interface – yes | Loopback interface – yes | Loopback interface – yes |
*For VM500 instance using version 9.1.0-h3, the maximum interfaces supported is 10.
**Console Access is read-only for Equinix-configured PAN devices.
Palo Alto Networks – Firewall (Self-Configured)
|
|
CPU = 2 cores Memory = 4G Disk size = 80G |
CPU = 4 cores Memory = 16G Disk size = 80G |
CPU = 8 cores Memory = 48G Disk size = 80G |
CPU = 16 cores Memory = 56G Disk size = 80G |
|---|---|---|---|---|
| Software Package | PANW-100 | PANW-300 | PANW-500 | PANW-700 |
| Minimum Interfaces Supported (# data interfaces available) |
10 | 10 | 10 | 10 |
| Maximum Interfaces Supported (# data interfaces available) |
10 | 19 | 19* | 19 |
| Allocated Resources |
CPU = 2 cores |
CPU = 4 cores |
CPU = 8 cores Memory = 16G Disk size = 80G |
CPU =16 cores Memory = 56G Disk size = 80G |
| Routing Domains |
MGMT |
MGMT |
MGMT |
MGMT |
| License Types Supported |
BYOL |
BYOL |
BYOL |
BYOL |
| Boot Time Average | 20 minutes | 20 minutes | 20 minutes | 20 minutes |
| BGP Local AS Support |
Yes | Yes | Yes | Yes |
| Access Methods | HTTPS Web UI |
HTTPS Web UI |
HTTPS Web UI |
HTTPS |
| Image Version |
9.0.0 9.0.1 9.0.4 9.1.0-h3 |
9.0.0 9.0.1 9.0.4 9.1.0-h3 |
9.0.0 9.0.1 9.0.4 9.1.0-h3 |
9.0.0 9.0.1 9.0.4 9.1.0-h3 |
| Restricted CLI Commands | ||||
| Throughput | Throughput (IMIX): 1 Gbps: IP-BASE (cvim: 2.4.15, 3.4.3); 360 Mbps: IP-SEC (9.0.0, 9.0.1)1500B IP-Base: 4 Gbps (cvim: 2.4.15, 3.4.3); 1350B IP-SEC: 640 Mbps | Throughput (IMIX): 2 Gbps: IP-BASE; 720 Mbps: IP-SEC1500B IP-Base: 6.4 Gbps; 1350B IP-SEC: 1.6 Gbps (9.0.1) | Throughput (IMIX): 5 Gbps: IP-BASE, 700 Mbps: IP-SEC (9.0.0), 1.5 Gbps: IP-SEC (9.0.1)1500B IP-Base: 12 Gbps, 1350B IP-SEC: 1.8 Gbps (9.0.0), 3.0 Gbps (9.0.1) | |
| Vendor Product Specs |
https://www.paloaltonetworks.com/resources/datasheets/vm-series-specsheet | |||
|
Services Offered
|
R Version Control |
|||
| Other Notes |
Loopback interface – yes | Loopback interface – yes | Loopback interface – yes | Loopback interface – yes |
*For VM500 instance using version 9.1.0-h3, the maximum interfaces supported is 10.
**Console Access is read-only for Equinix-configured PAN devices.
For information about creating a Palo Alto cluster, see Create a Palo Alto Cluster and Palo Alto Networks High Availability Cluster Guidance.
Important: If one or more devices in your cluster have to be deleted and re-created, the device(s) will have a new UUID. Manual intervention is necessary. You will have to associate the new UUID with your existing license.
