EasyManua.ls Logo

Netgate 5100 - Page 48

Netgate 5100
66 pages
To Next Page IconTo Next Page
To Next Page IconTo Next Page
To Previous Page IconTo Previous Page
To Previous Page IconTo Previous Page
Loading...
Product Manual, TNSR 19.02
(continued from previous page)
IPv6 Route Table: ipv6-VRF:0
counters:
received: 1925 bytes, 30 packets, 0 errors
transmitted: 1226 bytes, 19 packets, 0 errors
20 drops, 0 punts, 27 rx miss, 0 rx no buffer
The output shows that the interfaces are up and configured, and the counters show that a few packets have been
received.
It is now possible to verify connectivity to the VPC gateway on each subnet with the ping command. The VPC
gateway address is the base address of a subnet + 1. e.g.:
VPC gateway IP address for 10.5.0.0/24:
Base address 10.5.0.0 + 1 = 10.5.0.1
VPC gateway IP address for 10.5.1.0/24: 10.5.1.1
Base address 10.5.1.0 + 1 = 10.5.1.1
tnsr# ping 10.5.0.1 source 10.5.0.222 count 3
PING 10.5.0.1 (10.5.0.1) 56(84) bytes of data.
64 bytes from 10.5.0.1: icmp_seq=1 ttl=64 time=0.096 ms
64 bytes from 10.5.0.1: icmp_seq=2 ttl=64 time=0.231 ms
64 bytes from 10.5.0.1: icmp_seq=3 ttl=64 time=0.220 ms
--- 10.5.0.1 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 1999ms
rtt min/avg/max/mdev = 0.096/0.182/0.231/0.062 ms
tnsr# ping 10.5.1.1 source 10.5.1.218 count 3
PING 10.5.1.1 (10.5.1.1) 56(84) bytes of data.
64 bytes from 10.5.1.1: icmp_seq=1 ttl=64 time=0.071 ms
64 bytes from 10.5.1.1: icmp_seq=2 ttl=64 time=0.123 ms
64 bytes from 10.5.1.1: icmp_seq=3 ttl=64 time=0.157 ms
--- 10.5.1.1 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 1999ms
rtt min/avg/max/mdev = 0.071/0.117/0.157/0.035 ms
Interface Naming
The names that are displayed for Network Interfaces on an instance in the EC2 Web Console are different than the
names that appear in the TNSR CLI. The interfaces in TNSR are named using the PCI bus/slot/function of the device.
The names in the EC2 Web Console use the traditional Linux naming scheme and display as eth0, eth1, and so on.
In this example, it is straightforward to determine which interface in TNSR corresponds to an AWS Network Interface
in the EC2 Web Console because there are only 2 interfaces and one of them will be present at boot time.
If this instance has more Network Interfaces than in the example, or if it is unclear which interface in the TNSR
CLI matches up with which Network Interface in the EC2 Web Console, the two can be correlated by checking the
MAC addresses. The TNSR CLI command show interface will display all of the interfaces present and the
output includes the MAC address of each. The MAC address of each TNSR interface can be checked in the EC2 Web
Console to find the right Network Interface.
To find the MAC address of a Network Interface in the EC2 Web Console:
1. Navigate to https://console.aws.amazon.com/ec2/
1.2. Cloud Platforms 46