26.11.2012 Views

IronPort - CLI reference guide

IronPort - CLI reference guide

IronPort - CLI reference guide

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Chapter<br />

routeconfig<br />

Description<br />

Table 3-116 ping (Continued)<br />

64 bytes from 10.19.0.31: icmp_seq=5 ttl=64 time=0.125 ms<br />

64 bytes from 10.19.0.31: icmp_seq=6 ttl=64 time=0.124 ms<br />

64 bytes from 10.19.0.31: icmp_seq=7 ttl=64 time=0.122 ms<br />

64 bytes from 10.19.0.31: icmp_seq=8 ttl=64 time=0.126 ms<br />

64 bytes from 10.19.0.31: icmp_seq=9 ttl=64 time=0.133 ms<br />

64 bytes from 10.19.0.31: icmp_seq=10 ttl=64 time=0.115 ms<br />

^C<br />

--- anotherhost.example.com ping statistics ---<br />

11 packets transmitted, 11 packets received, 0% packet loss<br />

round-trip min/avg/max/stddev = 0.115/0.242/1.421/0.373 ms<br />

^C<br />

Note You must use Control-C to end the ping command.<br />

The routeconfig command allows you to create, edit, and delete static routes for<br />

TCP/IP traffic. By default, traffic is routed through the default gateway set with<br />

the setgateway command. However, <strong>IronPort</strong> AsyncOS allows specific routing<br />

based on destination.<br />

Routes consist of a nickname (for future <strong>reference</strong>), a destination, and a gateway.<br />

A gateway (the next hop) is an IP address such as 10.1.1.2. The destination can<br />

be one of two things:<br />

Cisco <strong>IronPort</strong> AsyncOS 7.6 <strong>CLI</strong> Reference Guide<br />

309

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!