Foundry NetIron MLX Series Installation and Basic Configuration Guide
4-8
© 2008 Foundry Networks, Inc.
December 2008
Testing Network Connectivity
After you cable the fiber-optic modules, you can test connectivity to other network devices by pinging those
devices. You also can perform trace routes.
Pinging an IP Address
To verify that a NetIron MLX Series router can reach another device through the network, enter a command such
as the following at any level of the CLI on the NetIron MLX Series router:
NetIron> ping 192.33.4.7
Syntax:
ping <ip addr> | <hostname> [source <ip addr>] [count <num>] [timeout <msec>] [ttl <num>] [size <byte>]
[quiet] [numeric] [no-fragment] [verify] [data <1-to-4 byte hex>] [brief]
Beginning with version 03.6.00 of the Multi-Service IronWare software, the maximum allowable size is 9170.
NOTE:
If you address the ping to the IP broadcast address, the device lists the first four responses to the ping.
Tracing a Route
To determine the path through which a NetIron MLX Series router can reach another network device, enter a
command such as the following at any level of the CLI on the NetIron MLX Series router:
NetIron> traceroute 192.33.4.7
Syntax:
traceroute <host-ip-addr> [maxttl <value>] [minttl <value>] [numeric] [timeout <value>]
[source-ip <ip addr>]
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
Foundry device displays up to three responses by default.
