Traffic from AWS hosts to the Versa FlexVNF hosted in the VPC?

Modified on: Wed, 29 Jul, 2020 at 8:08 PM

Applicable plans a b c d

Question: How to drive the traffic from AWS hosts to the Versa FlexVNF, hosted in the VPC?

Answer:

When the Versa FlexVNF is deployed in a Virual Private Cloud (VPC) as a Network Virtual Appliance (NVA), Enhanced Network Interfaces (ENI) are deployed on the LAN side of the Versa FlexVNF.

There are two methods to drive the traffic from AWS hosts to a Versa FlexVNF, hosted in the VPC:

Manually configure an IP static route on hosts or client machines keeping Versa FlexVNF LAN ENI IP as a next hop address.
Run the cli command on AWS device to modify the routing table associated with the LAN Subnet, referring Versa FlexVNF LAN ENI as a next hop address.

Sample CLI call:

aws ec2 create-route --route-table-id 
rtb-50007634 --destination-cidr-block 10.202.0.0/16
--network-interface-id eni-87d38382

In the first method, you need to add a static route to every host which is not a recommended in a real-time scenario.

The second method offers a much better solution, since you want to modify the AWS routing table associated with the LAN subnet and all the hosts use the same route.

NOTE: This configuration is not Versa release specific and applies to all the Versa FlexVNF SW versions deployed in AWS.

Did you find it helpful? Yes No