TMS zl Management and Configuration Guide ST.1.0.090213

D-102
Troubleshooting
Troubleshooting the TMS zl Module in Routing Mode
2. Check routes in the Network > Routing > Static Routes window and verify
that these routes exist:
• A route to the remote gateway
The TMS zl Module requires this route to set up the GRE tunnel.
• A route through the GRE tunnel to the remote network
If you do not see this route, the GRE tunnel is not correctly configured.
Select VPN > GRE > GRE Tunnels and edit the tunnel. Verify that the
remote network is listed in the Tunnel Traffic Selector.
Troubleshooting Routing
When the TMS zl Module is operating in routing mode, routing is always
enabled. If routing is also enabled on the host switch, it is important to ensure
that clients requiring protection are using the TMS zl Module as the default
gateway.
When you are troubleshooting routing problems, it may help to think of the
TMS zl Module as an external router. Routing peer or neighbor relationships
are established through the TMS zl Module’s port 1. (For example, if the TMS
zl Module is in slot C, routing relationships are established through port C1.)
Static Routes
Using static routes is the most basic routing option. Typically, you begin by
configuring a default route, which is also referred to as the route of last resort.
In addition to ensuring that the TMS zl Module has a static route to reach a
remote device, you must ensure that the remote device has a route back to
the TMS zl Module. Simple tools such as ping or traceroute are useful when
testing routing or connectivity.
RIP
You can configure the TMS zl Module to use RIP version 1, version2, or both.
It is important to ensure that the neighboring router supports compatible
versions.
A good place to start troubleshooting RIP is to confirm that a peer relationship
has been established. From the CLI, enter:
hostswitch(tms-module-C)# show ip rip peer