Validate the VNET

At this point you should have a fully working VNET with a custom NFV appliance providing routing.

Validate the VNET by verifying the application assigned to VNET-ID-01:

# Guest has static IP in VNET subnet 
[root@app-01 ~]# ip addr show dev eth0 
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000 
   link/ether b4:d1:35:00:23:4e brd ff:ff:ff:ff:ff:ff 
    inet 100.127.4.1/24 brd 100.127.4.255 scope global eth0 
       valid_lft forever preferred_lft forever 
    inet6 fe80::b6d1:35ff:fe00:234e/64 scope link 
       valid_lft forever preferred_lft forever 

# Default route is pointed at Inside interface of NFV 
[root@app-01 ~]# ip route 
default via 100.127.4.254 dev eth0 
100.127.4.0/24 dev eth0 proto kernel scope link src 100.127.4.1 
169.254.0.0/16 dev eth0 scope link metric 1002 

# NFV is routing traffic for guest traffic 
[root@app-01 ~]# ping www.google.com 
PING www.google.com (172.217.10.100) 56(84) bytes of data. 
64 bytes from lga34s15-in-f4.1e100.net (172.217.10.100): icmp_seq=1 ttl=53 time=12.6 ms 
64 bytes from lga34s15-in-f4.1e100.net (172.217.10.100): icmp_seq=2 ttl=53 time=9.49 ms 
--- www.google.com ping statistics --- 
2 packets transmitted, 2 received, 0% packet loss, time 1002ms 
rtt min/avg/max/mdev = 9.498/11.090/12.683/1.595 ms