Cisco Catalyst 8000v - Specifications
Cisco Catalyst 8000v
This section summarises the platform-visible specifications for the Cisco Catalyst 8000v SDWAN Gateway. Use the Creation guide to provision an instance and this page for deployment options, interfaces, required service parameters and platform outputs.
Flavors
Select compute sizing using the available flavors. The platform renders the supported sizes below.
| Standard | DPDK | |
|---|---|---|
| Small | 2 vCPU 4 GB Mem 64 GB Disk | 2 vCPU 4 GB Mem 64 GB Disk |
| Medium | 4 vCPU 8 GB Mem 64 GB Disk | 4 vCPU 8 GB Mem 64 GB Disk |
| Large | 8 vCPU 16 GB Mem 64 GB Disk | 8 vCPU 16 GB Mem 64 GB Disk |
In dual deployment mode you may choose a flavor per virtual device.
Interfaces
The diagram above shows a simplified deployment: one Catalyst 8000v virtual device and the numbered interfaces that connect it to the public Internet and MPLS services. VLAN sub-interfaces on the MPLS-facing interface are summarised as a range for readability.
Common interface behaviour
- VLAN sub-interfaces on the MPLS interface are configured as a set (VLANs 101–148). Do not enumerate all VLANs in the UI; provide VPN entries per sub-interface when prompted.
- Public IP addresses attached to the Internet interface are platform-allocated outputs. To request extra public IPv4 addresses, use the Added IP address number parameter during provisioning.
#1 - Internet Interface
Role: External / public access (optional). The platform allocates at least one public IP for this interface and displays it as an informational output after provisioning.
- Added IP address number — Request additional public IPv4 addresses on the Internet interface. Enter an integer between 1 and 8 to request up to 8 extra addresses. This setting is optional and updatable.
- Public IP address — Allocated by the platform and shown in deployment results; no customer action is required to obtain the primary address.
#2 - MPLS-VPN interface
Role: Business VPN attachments using VLAN sub-interfaces.
- VLANs are presented as sub-interfaces (range 101–148). For each VLAN sub-interface you provide a VPN list with one or more VPN entries.
- VPN list — An array of VPN entries (min 1, max 99). Each item includes VPN Name and optional VPN role.
- VPN Name — BVPN alias string (pattern: [a-zA-Z0-9-_]*). Provide the alias exactly as supplied by your MPLS operator.
- VPN role — Select one of any-to-any, client or server.
- Enable BGP — Optional boolean (default: false). Toggle only when you require BGP peering on that VLAN/sub-interface.
- AS prepend — Optional integer (1..6). The specification notes this applies for backup VM scenarios; provide only when instructed by your operator.
#3 - MPLS-VPN Interface - transport
Role: Optional transport interface for MPLS connectivity and static routes.
- Static route — Optional list of routes. Provide prefixes in IPv4 CIDR format and optional community tags when required by your design.
- The platform exposes transport subnet gateway information as informational outputs after provisioning.
Software device versions
Available software images are listed below. Use the full image token when selecting an image in the provisioning UI.
- 17-12-3
Virtual device parameters
These parameters apply at the virtual device level:
- VM name — Hostname used as the resource identifier. Provide a value matching the allowed pattern (max length 22, pattern [a-zA-Z0-9-]*).
- VM image — Choose the Catalyst 8000v image variant from the image dropdown; use the full image token as displayed.
- VM flavor — Select one of the supported flavors (for example: std1.c2, std1.c4, std1.c8 or their DPDK equivalents). Flavors determine vCPU/RAM sizing.
- VM AS number — Autonomous System number for BGP (range 1..4294967295). Provide only if BGP peering is required; this value is not updatable after creation.
Service specific parameters
Service-specific parameters are required service-level values provided during provisioning. They are not interface IPs or platform outputs; they are injected into the device initialization (cloud-init) and used by the vendor bootstrap process.
- UUID (mandatory, not updatable): Unique service identifier required for provisioning. Provide the UUID requested by the onboarding process.
- One time Password (mandatory, not updatable): OTP token used during device bootstrap. Provide the token exactly as supplied; values are treated as credentials.
- Organization name (mandatory, not updatable): Organization identifier used in cloud-init templates.
- Vbond IP address or FQDN (mandatory, not updatable): IP address or DNS name of the SD-WAN controller endpoint the device must contact. Pattern constrained to names/addresses accepted by the provisioning form.
- System IP (mandatory, not updatable): IPv4 address used by the device for control-plane identification in SD-WAN.
- Site id (mandatory, not updatable): Numeric site identifier used by vendor provisioning (integer range 1..4294967295).
- Password (mandatory, not updatable): Administrative password created during device bootstrap (hidden in the UI).
Provide these values in the custom parameters section of the creation flow. All listed items above are mandatory per the blueprint and are not updatable after provisioning.
Platform-generated outputs
- Public IP address — Public IPv4 addresses allocated by the platform for the Internet interface are informational outputs visible after provisioning.
- Gateway address — Gateway IP for the MPLS transport subnet is provided as an informational output for the transport interface.
Useful links
Licence
Only Bring Your Own Licence (BYOL) type is supported for Fortinet SD-WAN. You need to purchase your software licence with Fortinet sales.
Security group
No default security group configured for Fortinet VNE model.