13-25
Cisco Intrusion Prevention System Sensor CLI Configuration Guide for IPS 5.0
78-16527-01
Chapter 13 Administrative Tasks for the Sensor
Tracing the Route of an IP Packet
Name: "Power Supply", DESCR: ""
PID: ASA-180W-PWR-AC, VID: V01 , SN: 123456789AB
sensor#
sensor#
show inventory
Name: "Module", DESCR: "ASA 5500 Series Security Services Module-20"
PID: AIP-SSM-20, VID: V01 , SN: JAB0815R036
sensor#
sensor-4240#
show inventory
Name: "Chassis", DESCR: "IPS 4240 Appliance Sensor"
PID: IPS-4240-K9, VID: V01 , SN: P3000000653
sensor-4240#
You can use this information when dealing with the TAC.
Tracing the Route of an IP Packet
Use the
trace
ip_address
count
command to display the route an IP packet takes to a destination. The
ip_address
option is the address of the system to trace the route to. The
count
option lets you define how
many hops you want to take. The default is 4. The valid values are 1 to 256.
Caution
There is no command interrupt available for this command. It must run to completion.
To trace the route of an IP packet, follow these steps:
Step 1
Log in to the CLI.
Step 2
Display the route of IP packet you are interested in:
sensor#
trace 10.1.1.1
traceroute to 10.1.1.1 (10.1.1.1), 4 hops max, 40 byte packets
1 10.89.130.1 (10.89.130.1) 0.267 ms 0.262 ms 0.236 ms
2 10.89.128.17 (10.89.128.17) 0.24 ms * 0.399 ms
3 * 10.89.128.17 (10.89.128.17) 0.424 ms *
4 10.89.128.17 (10.89.128.17) 0.408 ms * 0.406 ms
sensor#
Step 3
To have the route take more hops than the default of 4, use the
count
option:
sensor#
trace 10.1.1.1 8
traceroute to 10.1.1.1 (10.1.1.1), 8 hops max, 40 byte packets
1 10.89.130.1 (10.89.130.1) 0.35 ms 0.261 ms 0.238 ms
2 10.89.128.17 (10.89.128.17) 0.36 ms * 0.344 ms
3 * 10.89.128.17 (10.89.128.17) 0.465 ms *
4 10.89.128.17 (10.89.128.17) 0.319 ms * 0.442 ms
5 * 10.89.128.17 (10.89.128.17) 0.304 ms *
6 10.89.128.17 (10.89.128.17) 0.527 ms * 0.402 ms
7 * 10.89.128.17 (10.89.128.17) 0.39 ms *
8 10.89.128.17 (10.89.128.17) 0.37 ms * 0.486 ms
sensor#
