Link to home
Start Free TrialLog in
Avatar of timbrigham
timbrighamFlag for United States of America

asked on

Tracert output

I'm in the process of migrating from an old PIX 6.3(3) to a Forefront 2010 server. During this process I'll have both systems running side by side for a while.
I want to verify that I've successfully changed the gateway for a subset of my systems. The PIX doesn't show up as a hop in tracert:

tracert 4.2.2.2
Tracing route to vnsc-bak.sys.gtei.net [4.2.2.2]
over a maximum of 30 hops:
  1    <1 ms    <1 ms    <1 ms  192.168.20.1
(PIX should be here, 192.168.250.1)
  2     1 ms    <1 ms    <1 ms  65.X.X.105 - the IP of our ISP's gateway

How can I easily distinguish the route for this point using tracert? I'm hoping to either get the PIX to be included in the output or a sample of what to look for for traffic successfully routed to  Forefront.
ASKER CERTIFIED SOLUTION
Avatar of MikeKane
MikeKane
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of ivarson408
ivarson408

192.168.20.1 appears to be a router or gateway? This is routing it to the next spot so you should check the routing config on that device.
Avatar of timbrigham

ASKER

Thanks gentlemen.

192.168.20.1 is an aging Cisco 2811. The PIX is long out of coverage so upgrading isn't an option.
It looks like "sho ip cef exact-route 192.168.20.254 4.2.2.2" should do what I need.

I'm using a route-map applied to a couple interfaces to collect the subset of computers I want to test with. Can I expect the output of this command will accurately reflect the route map?
I would 'assume' yes.      I've never seen the 'show exact route' to give an incorrect path that differed from the config.    


Many thanks.