Selecting, Sizing & Configuring a VNF
You configure a VNF in the TCx Portal by choosing its function, vendor and model, its size, its licensing and management model, and its software version, then linking it to a Fabric Port with an edge connection. This page lists the fields; the available vendors, models, sizes and OS versions are in the Vendors & Devices section.
VNF configuration fields
|
Field |
What it is |
Mandatory |
Sample value |
|
Alias Name |
A friendly identifier used to link this VNF to other components in the solution. |
Yes |
Router_Delhi |
|
Device Category |
The function type: Router, Firewall or SD-WAN. For other categories, contact your account team. |
Yes |
Router |
|
Deployment Location |
The IZO™+ Multi Cloud Connect location where the VNF is deployed. |
Yes |
Delhi |
|
Data Center |
The data centre within the chosen IZO™+ Multi Cloud Connect location. |
Yes |
Sample DC, India |
|
Vendor |
The VNF vendor. |
Yes |
Cisco |
|
Device Make & Model |
The specific model from that vendor. |
Yes |
Catalyst 8000V (Autonomous Mode) |
|
VNF Size |
The T-shirt size; pricing follows the allocated vCPU cores (for example 2, 4, 8 or 16 cores). |
Yes |
Tiny (2 cores, 8 GB) |
|
Licensing |
Tata Subscription (Tata Communications provides the licence) or BYOL (you provide it). |
Yes |
Tata Subscription |
|
Management |
Tata Managed or Customer Managed. |
Yes |
Tata Managed |
|
Software Package |
The software/feature package for the model. |
Yes |
DNA Advantage |
|
License Tier |
The throughput tier, where the model uses one. |
Where applicable |
Tier 1 |
|
Software OS Version |
The operating-system version for the VNF. |
Yes |
17.12.2 |
|
Link Type |
Single (one connection) or Dual (two connections for high availability). |
Yes |
Single |
|
Number of Interfaces |
The number of interfaces on the VNF. |
Yes |
24 |
|
AS Number (Global) |
The global AS number, where a unified ASN is used. |
Where applicable |
64550 |
Sizing
VNF size is expressed as a T-shirt size - Tiny, Small, Medium, Large (and, for some models, Extra Large) - which maps to a fixed number of vCPU cores and an amount of memory. Larger sizes give more throughput and, where relevant, a higher licence tier. Choose the size from your expected throughput and feature needs; the size-to-core/memory mapping for each model is in the Vendors & Devices section.
Linking the VNF to a Fabric Port A VNF is joined to a Fabric Port with an edge connection, which carries a bandwidth and links the A-end Fabric Port to the Z-end VNF. A dual-link edge connection provides redundancy and needs two Fabric Ports. After you place or change any component, validate it again before submitting.
Ordering and changing a VNF
A VNF is one of the two components you can order on its own (the other is a Tata Cloud Router); everything else is ordered within a solution. Once a service is Active you can extend it with MACD - for example, adding a Cloud VC to an existing VNF to reach another cloud. See Order Tracking & Status.
What’s on the cloud side
The cloud connection beyond the VNF is created in the cloud provider’s console. This page covers how the VNF is selected and configured on the Tata Communications side; for the cloud-side connection request and routing, see the relevant per-cloud section.