Brocade FastIron Ethernet Switch Administration Guide - Manual (Page 112)

Tracing an IPv4 route
NOTE
This section describes the IPv4traceroute command. For details about IPv6traceroute , refer to the
FastIron Ethernet Switch Layer 3 Routing Configuration Guide .
Use the traceroute command to determine the path through which a Brocade device can reach
another device. Enter the command at any level of the CLI.
The CLI displays trace route information for each hop as soon as the information is received.
Traceroute requests display all responses to a given TTL. In addition, if there are multiple equal-cost
routes to the destination, the Brocade device displays up to three responses by default.
device> traceroute 10.33.4.7
Syntax: traceroute host-ip-addr [ maxttl value ] [minttl value ] [numeric][timeoutvalue] [ source-ip
ip-addr ]
Possible and default values are as follows.
minttl - minimum TTL (hops) value: Possible values are 1 - 255. Default value is 1 second.
maxttl - maximum TTL (hops) value: Possible values are 1 - 255. Default value is 30 seconds.
timeout - Possible values are 1 - 120. Default value is 2 seconds.
numeric - Lets you change the display to list the devices by their IP addresses instead of their names.
source-ip ip-addr - Specifies an IP address to be used as the origin for the traceroute.
Hitless management on the FSX 800 and FSX 1600
Hitless management is supported on the FSX 800 and FSX 1600 chassis with dual management
modules. It is a high-availability feature set that ensures no loss of data traffic during the following
events:
• Management module failure or role change
• Software failure
• Addition or removal of modules
• Operating system upgrade
During such events, the standby management module takes over the active role and the system
continues to forward traffic seamlessly, as if no failure or topology change has occurred. In software
releases that do not support hitless management, events such as these could cause a system reboot,
resulting in an impact to data traffic.
The following Hitless management features are supported:
Hitless Switchover - A manually controlled (CLI-driven) switchover of the active and standby
management modules without any packet loss to the services and protocols that are supported by
Hitless management. A switchover is activated by the CLI command switch-over-active-role .
Hitless Failover - An automatic, forced switchover of the active and standby management modules
because of a failure or abnormal termination of the active management module. In the event of a
failover, the active management module abruptly leaves and the standby management module
immediately assumes the active role. Like a switchover, a failover occurs without any packet loss to
hitless-supported services and protocols. Unlike a switchover, a failover generally happens without
warning.
Tracing an IPv4 route
112 FastIron Ethernet Switch Administration Guide
53-1003075-02