To verify a route for the virtual router, perform the following steps:
Open the Command Line Interface (CLI). For more information on how to open the CLI, go to Accessing the Command Line Interface Using Telnet.
Enter get route; press ENTER.
C - Connected, S - Static, A - Auto-Exported, I - Imported, R - RIP iB - IBGP, eB - EBGP, O - OSPF, E1 - OSPF external type 1 E2 - OSPF external type 2 trust-vr (2 entries)
----------------------------------------------------------------------------------------------------------------
ID IP-Prefix Interface Gateway P Pref Mtr Vsys
*2 192.168.1.0/24 eth1 0.0.0.0 C0 0 Root
*3 1.1.1.0/24 eth3 0.0.0.0 C0 0 Root Unless the peer VPN gateway was directly connected to same subnet as this device, the NetScreen will not know where to send an outgoing packet destined for a subnet that is not the same as its own default gateway. It is a good practice on a NetScreen device to always specify a default route in the routing table in case the NetScreen does not know where to route a packet. This can be true even for directly connected devices on the subnet.
To verify that there is a route to the destination IP, enter get route ip [ip address of the destination ip]; press ENTER.
ns208-> get route ip 1.1.1.2
Destination Routes for 1.1.1.2
---------------------
trust-vr : => 1.1.1.1/24 (id=3) via 0.0.0.0 (vr: trust-vr)
Interface ethernet3 , metric 0
This indicates that there is a route in the trust-vr via a directly connected interface eth3.
