How to Verifying Your Configuration

How to Verifying Your Configuration

Once you take a look at the running-config, and it appears that everything is in order, you can verify your configuration wit

Router#ping ?
WORD Ping destination address or hostname
appletalk Appletalk echo
decnet DECnet echo
ip IP echo
ipx Novell/IPX echo
srb srb echo

<cr>


2. You can also use the traceroute program to find the path a packet takes as it traverses an

internetwork. Traceroute can also be used with multiple protocols.


Router#      traceroute ?

WORD       Trace route to destination address or  hostname

appletalk      AppleTalk Trace
clns              ISO CLNS Traceip 
IP                 Trace
oldvines       Vines Trace (Cisco)
vines            Vines Trace (Banyan)

<cr>

3. Telnet can be used to test IP connectivity and to gain access into remote routers. From the
router prompt, you do not need to type the telnet command. If you just type a hostname or IP
address, it will assume you want to telnet. The following example shows how to use telnet from
a router prompt. However, you need to have a configured and working network for telnet to be

successful. We'll use telnet more in the rest of the chapters.



Router#telnet ?
WORD IP address or hostname of a remote system

<cr>



4. Another way to verify your configuration is by typing show interface commands. The first
command is show interface ?, which shows us all the available interfaces to configure.
The only interfaces that are not logical are Ethernet and Serial.




Router#sh int ?
Ethernet         IEEE 802.3

Null               Null interface
Serial             Serial

accounting     Show interface accounting
crb                 Show interface routing/bridging info
irb                 Show interface routing/bridging info

<cr>



6. Use the show controllers command to display information about the physical interface itself.
It will also give you the type of serial cable plugged into a serial port. Typically this will only be
a DTE cable, which then plugs into a type of Data Service Unit (DSU).


Router#sh controllers s 0
HD unit 0, idb = 0x1229E4, driver structure at 0x127E70
buffer size 1524 HD unit 0, V.35 DTE cable
cpb = 0xE2, eda = 0x4140, cda = 0x4000


Router#sh controllers s 1
HD unit 1, idb = 0x12C174, driver structure at 0x131600
buffer size 1524 HD unit 1, V.35 DCE cable
cpb = 0xE3, eda = 0x2940, cda = 0x2800


Notice that serial 0 has a DTE cable, whereas the serial 1 connection has a DCE cable. Serial
1 would have to provide clocking with the clock rate command. Serial 0 would get it's
clocking from the DSU. Also, understand that this is the only command that needs to have a

space after the serial command.