Cisco Tips & Tricks

May 23, 2006

Troubleshooting dial-peers

Filed under: Router — ciscotips @ 11:15 pm

When troubleshooting dial-peers in a voice over IP (VoIP) environment, you can use the call simulate command to simulate calling to a dial-peer’s destination pattern (csim start number). This command enables you to verify that your dial-peer is configured properly, that there are no hardware problems, and that you are reaching the destination you want (provided that a ringing device is connected to the called port). For example:
Router#csim start number <number> where <number> is the destination pattern of the dial-peer you are testing

Changing enable password for a Remote Router

Filed under: Router — ciscotips @ 11:11 pm

Telnet into the router and log in to enable mode, then Telnet out to another router to Telnet back into the same router again. Change the enable password, exit to global configuration mode, and try to log in to enable mode. If this fails, you can exit from the Telnet session twice until you get back to the same router where you are still in enable mode. This allows you to change the enable password again.

Router1#telnet router2
Router2>telnet router1
Router1#enable secret
Router1> enable
Access denied

Auditing Router Interfaces

Filed under: Router, Switching — ciscotips @ 11:01 pm

I received a following tip from  Robert in california, incorporating here:- 

Maintenance Finding Router Interface Information I sometimes need to audit a listing of all interfaces on a router or Multiswitch Feature Card (MSFC) for the IP address and description. While there are ways to get either  (for example, show ip int brief and sh int desc), I have been looking for a command that enables me to display both types of information at once. To find the exact information that I need quickly, I use the following command: 

show run | include interface | ip address | description

Connecting a new switch

Filed under: Switching — ciscotips @ 10:57 pm

 When connecting a new switch to your network you can accidentally change your current VLAN database if the new switch has a higher VLAN Trunking Protocol (VTP) revision number. To avoid this, you must clear the VTP revision number on the new switch. The easiest way is to change the VTP domain name to “something_else” and back to “your_VTP_domain” on the new switch. This sets the VTP revision number to 0 and you can connect the switch to the network without any problem.

Create a free website or blog at