Aller au contenu principal

Cisco Catalyst 8000v - Specifications

Cisco Catalyst 8000v​

This page describes the customer-facing specifications for the Cisco Catalyst 8000v virtual router. The VNF deploys the Catalyst 8000v image on one or two virtual devices depending on the selected deployment mode (single or dual). The sections below explain flavors, interfaces, routing options, VM parameters and platform-generated outputs.

Flavors​

Select the compute size for each virtual device using the flavor table below. DPDK variants are available for use cases that require DPDK-capable forwarding.

StandardDPDK
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 deployments, a flavor can be chosen independently for each virtual device.

Interfaces​

Simplified topology: the Catalyst 8000v VM connects to the Internet via a floating public IP attached to the #1 - Internet Interface. The MPLS-VPN connectivity is provided on #2 - MPLS-VPN interface using VLAN sub-interfaces (101–148); those VLANs are grouped in the diagram for readability and listed in the Interfaces section. Loopback is shown as an Internet loopback on the VM.

Common behaviour for interfaces:

  • The primary public IPv4 address for the Internet interface is a platform-generated output and shown in the portal after provisioning.
  • Customers can request additional public IPs using the Added IP address number parameter (1..8). This value is optional and updatable.

#1 - Internet Interface​

  • Role: External connectivity (Internet). A floating public IP is attached to this interface and displayed by the platform as an informational output.
  • Customer inputs: none required for the primary public IP. Use Added IP address number to request 1 to 8 additional public IPv4 addresses; this parameter is optional and updatable during the VNF lifecycle.

#2 - MPLS-VPN interface​

  • Role: Business VPN connectivity to the MPLS provider using VLAN sub-interfaces.
  • VLAN support: VLAN sub-interfaces 101–148 are supported and each VLAN is optional. VLANs are presented as a grouped range in the topology diagram for readability.
  • Per VLAN options (applies to each defined VLAN sub-interface):
    • VPN list: select one or more VPN aliases (1..99 items) to attach the VLAN to an MPLS VPN.
    • VPN Name: an alphanumeric alias identifying the VPN (pattern: [a-zA-Z0-9-_]*).
    • VPN role: one of any-to-any, client, server.
    • Enable BGP: optional boolean to enable BGP on the VLAN sub-interface. Default is false.
    • AS prepend: optional integer (1..6). The blueprint description marks this as intended for backup VM scenarios; treat it as an advanced setting and provide values only when required by your network design.

Do not repeat per-VLAN tables for each VLAN in the portal; the platform UI groups per-VLAN controls and validates counts and patterns when you add VLAN entries.

Routing and BGP​

The BGP settings are available per VLAN sub-interface on the MPLS connection:

  • The Enable BGP option is optional and updatable per VLAN. When BGP is not enabled on a VLAN, no BGP-specific configuration is applied through that setting.
  • The AS prepend value is an optional, advanced integer (1..6). It is described in the blueprint as intended for backup VM scenarios; provide this value only when instructed by your network design or operations team.
  • The VM AS number is a VM-level setting used when BGP is configured on the device; it accepts 2- or 4-byte AS numbers.

Virtual device parameters​

  • VM name: hostname used as the device identifier. Provide a valid hostname (pattern and length enforced by the portal).
  • VM image: select the Catalyst 8000v image version to deploy (for example: c8000v-17-12-3-8G-VGA is listed in the supported image set). Image choices are shown in the Software list below.
  • VM flavor: choose from the available flavors to set CPU and memory. DPDK flavors are available when required by forwarding needs (see Flavor table above).
  • VM AS number: optional autonomous system number for the VM (1..4294967295); provide this when you plan to enable BGP and require a specific AS on the device.

Service-specific parameters​

  • Admin password (mandatory, sensitive): the initial password for the device admin account. The platform hides this value in the portal and uses it during provisioning to create the administrative account on the virtual router. Provide a secure password at creation time.

Platform-generated outputs​

  • Public IP address (primary): the primary IPv4 address allocated by the platform and attached to the #1 - Internet Interface. This is a platform-generated, informational output displayed after provisioning.
  • Loopback IP (Internet): a loopback IPv4 address automatically configured on the device for Internet adjacency; shown as a platform-generated output.

Software device versions​

Below are the software image versions available for this VNF.

  • 17.12.3
Cisco Support - Routers and Software Downloads
Cisco Support - Documentation and Downloads

Licence​

Only Bring Your Own Licence (BYOL) type is supported for Fortinet SDWAN. You need to purchase your software licence with Fortinet sales.

Security group​

No default security group configured for Fortinet VNE model.