Cisco Routers for the Desperate

This is a short book that can be read in a single sitting. However, like most hands-on technology books, it’s best to read it in front of a computer accessing the resource being discussed. In this case, a Telnet session with a Cisco router is the fastest way to learn and retain the survival lessons taught. Author Michael Lucas has obviously read many of those thick Cisco router management books, and has effectively distilled the most important morsels of information into this brief handbook. By Chapter 4 (there are nine chapters in all, plus a useful Appendix on IP addresses and netmasks), the book had worked its magic on me. The black rectangular Cisco box sitting in the server rack was no longer the mysterious 2001-like monolith that hummed along and somehow had something to do with delivering my executing Web code to the world. Rather, it was just another computer that could be told what to do. More importantly, it was now a system that I could understand — and even troubleshoot when the time came.

The book quickly teaches readers about working with the Cisco command line, which is the entry path into router configuration, management, WAN connections, and even upgrading Cisco’s Internetwork Operating System (IOS). Chapter 5 on troubleshooting routers is the book’s most important section, and is the real reason behind buying the book in the first place. Focusing on the two primary problem areas for routers (crashes and/or network failure or slowness), the suggestions offered should ideally be incorporated into a disaster recovery procedure for router recovery. At 25 pages, Chapter 7 on redundancy with BGP and HSRP is the book’s lengthiest and most complex chapter, requiring a re-read to grok all the router concepts and blocks of capital letters (ARIN, ASN, BGP, HSRP, MRTG, and RADB). Nevertheless, once these initially cryptic concepts are understood, they not only make sense, they also bring an even deeper appreciation for the complexity that Cisco routers are capable of managing.

Download:

http://rapidshare.com/files/12916306/Cisco_Routers_For_The_Desperate_Router_Management_The_Easy_Way.zip

H.323 versus SIP: A Comparison

Philosophy

H.323 was designed with a good understanding of the requirements for multimedia communication over IP networks, including audio, video, and data conferencing. It defines an entire, unified system for performing these functions, leveraging the strengths of the IETF and ITU-T protocols.
As a result, it might be reasonable for users to expect about the same level of robustness and interoperability as is found on the PSTN today, although this admittedly varies across the globe.
H.323 was designed to scale to add new functionality. The most widely deployed use of H.323 is "Voice over IP" followed by "Videoconferencing", both of which are described in the H.323 specifications

SIP was designed to setup a "session" between two points and to be a modular, flexible component of the Internet architecture. It has a loose concept of a call (that being a "session" with media streams), has no support for multimedia conferencing, and the integration of sometimes disparate standards is largely left up to each vendor.
As a result, SIP is now a 10-year old protocol with a vast number of interoperability problems. While SIP has been successfully deployed in some environments, those are generally "closed" environments where the means of interoperability has been PSTN gateways.

Reliability

H.323 has defined a number of features to handle failure of intermediate network entities, including "alternate gatekeepers", "alternate endpoints", and a means of recovering from connection failures

SIP has not defined procedures for handling device failure. If a proxy fails, the user agent detects this through timer expiration. It is the responsibility of the user-agent to send a re-INVITE to another proxy, leading to long delays in call establishment.

Message Definition
H.323-> ASN.1, a standardized, extremely precise, easy-to-understand structural notation that is used by many other systems.

SIP->ABNF, or Augmented Backus-Naur Form, a syntactical notation. SIP uses the ABNF as defined in RFC 2234

Message Encoding
H.323 encodes messages in a compact binary format that is suitable for narrowband and broadband connections. Messages are efficiently encoded and decoded by machines, with decoders widely available (e.g., Ethereal).

SIP messages are encoded in ASCII text format, suitable for humans to read. As a consequence, the messages are large and less suitable for networks where bandwidth, delay, and/or processing are a concern.
SIP messages get so large that they sometimes exceed the MTU size when going over WAN links, resulting in delays, packet loss, etc. As a result, effort has been made to binary encode SIP (e.g., RFC 3485 and RFC 3486).

Media Transport
H.323 - RTP/RTCP, SRTP

SIP - RTP/RTCP, SRTP

Extensibility -Vendor Specific
H.323 is extended with non-standard features in such a way as to avoid conflicts between vendors. Globally unique identifiers prevent feature and data element collision.

SIP is extended by adding new header lines or message bodies that may be used by different vendors to serve different purposes, thus risking interoperability problems.

Extensibility -Standard

H.323 is extended by the standards community to add new features to H.323 in such a way as to not impact existing features. However, new revisions of H.323 are published periodically, which introduce new functionality that is mandatory, yet done in such a way as to preserve backward compatibility

SIP is extended by the standards community to add new features to SIP in such a way as to not impact existing features. However, new revisions of SIP are potentially not backward compatible (e.g., RFC 3261 was not entirely compatible with RFC 2543). In addition, several extensions are "mandatory" in some implementations, which cause interoperability problems

Scalability -Load Balancing

H.323 has the ability to load balance endpoints across a number of alternate gatekeepers in order to scale a local point of presence. In addition, endpoints report their available and total capacity so that calls going to a set of gateways, for example, may be best distributed across those gateways.

SIP has no notion of load balancing, except "trial and error" across pre-provisioned devices or devices learned from DNS SRV records. There is no means of detecting the load on a particular gateway or to know whether a device has failed, meaning that proxies simply have to try a PSTN gateway, wait for the call to timeout, and then try another

Scalability -Call Signaling
When an H.323 gatekeeper is used, it may simply provide address resolution through one RAS message exchange, or it may route all call signaling traffic. In large networks, the direct call model may be used so that endpoints connect directly to one another.

When using a SIP proxy to perform address resolution for the SIP device, the proxy is required to handle at least 3 full message exchanges for every call. In large networks, such as IMS networks, the number of messages on the wire may be excessive. A basic call between two users may require as many as 30 messages on the wire!

Scalability -Statelessness

An H.323 gatekeeper can be stateless using the direct call model.
A SIP proxy can be stateless if it does not fork, use TCP, or use multicast

Scalability -Address Resolution
H.323 defines an interface between the endpoint and gatekeeper for address resolution using ARQ or LRQ. The H.323 gatekeeper may use any number of protocols to discover the destination address of the callee, including LRQs to other gatekeepers, Annex G/H.225.0, TRIP, ENUM, and/or DNS. The endpoint does not have to be concerned with the mechanics of this process, and the processing requirements for address resolution placed on the gatekeeper by H.323 are for just a single message exchange.

While SIP has no address-resolution protocol, per se, a SIP user agent may route its INVITE message through a proxy or redirect server in order to resolve addresses. The SIP proxy may use various protocols to discover the destination address of the callee, including TRIP, ENUM, and/or DNS. The endpoint does not have to be concerned with the mechanics of this process. Unfortunately, the processing requirements placed on the SIP proxy are higher than with H.323 because at least 3 message exchanges must take place between the SIP device, SIP proxy, and the next hop.

Addressing

Flexible addressing mechanisms, including URIs, e-mail addresses, and E.164 numbers.
H.323 supports these aliases:
E.164 dialed digits
generic H.323 ID
URL
transport address
email address
party number
mobile UIM
ISUP numberH.323 also supports overlap sending with no additional overhead, except conveyance of the newly received digits in a single message.

SIP only understands URI-style addresses. This works fine for SIP-SIP devices, but causes some confusion when trying to translated various dialed digits. The unofficial convention is that a "+" sign is inserted in the SIP URI (e.g., "sip:+18005551212@example.com") in order to indicate that the number is in E.164 format, versus a user ID that might be numeric.
SIP has support for overlapped signaling defined in RFC 3578, though additional digit received requires transmission of three messages on the wire (a new INVITE, a 484 response to indicate that the address is incomplete, and an ACK).

Billing
Even with H.323's direct call model, the ability to successfully bill for the call is not lost because the endpoint reports to the gatekeeper the beginning and end time of the call via the RAS protocol. Various pieces of billing information may be present in the ARQ and DRQ messages at the start and end of the call

If the SIP proxy wants to collect billing information, it has no choice but to stay in the call signaling path for the entire duration of the call so that it can detect when the call completes. Even then, the statistics are skewed because the call signaling may have been delayed. Otherwise, there is no mechanism in SIP to perform any accounting/billing function.

Call Setup

A call can be established in as few as 1.5 round trips using UDP:
Setup -> <- Connect Ack ->
Of course, more elaborate call establishment procedures may be required to negotiate complex capabilities, negotiate complex video modes, etc.

A call can be established in as few as 1.5 round trips using UDP:
INVITE -> <- 200 OK Ack ->
Most real-world flows are more complex, as they often pass through one or more proxy devices, have intermediary response messages, and "negotiate" capabilities through a "trial and error" process that is far from scientific.

Capability Negotiation
H.323 entities may exchange capabilities and negotiate which channels to open, including audio, video, and data channels. Individual channels may be opened and closed during the call without disrupting the other channels.

SIP entities have limited means of exchanging capabilities. RFC 3407 is the state of the art, which is more or less a "declaration" mechanism, not a negotiation procedure. The end result is still a "trial and error" approach in case the called party does not support the proposed media

Call Forking

H.323 gatekeeper can control the call signaling and may fork the call to any number of devices simultaneously.

SIP proxies can control the call signaling and may fork the call to any number of devices simultaneously.

PSTN Interworking
H.323 borrows from traditional PSTN protocols, e.g., Q.931, and is therefore well suited for PSTN integration. However, H.323 does not employ the PSTN's circuit-switched technology--like SIP, H.323 is completely packet-switched. How Media Gateway Controllers fit into the overall H.323 architecture is well-defined within the standard.

SIP has no commonality with the PSTN and such signaling must be "shoe-horned" into SIP. SIP has no architecture that describes the decomposition of the gateway into the Media Gateway Controller and the Media Gateways. This has been a recent study of 3GPP and others in the form of IMS. Presently, there are about 4 "IMS" variants: 3GPP, ITU NGN, 3GPP2, and PacketCable. Pick the architecture you like best, I suppose.


Services
H.323 Services may be provided to the endpoint through a web-browser interface using HTTP or a feature server using Megaco/H.248. In addition, services may be provided to an endpoint as it places a call, as a call arrives, or during the middle of a call by a gatekeeper or other entity that routes the call signaling. As a result, H.323 is well-suited to providing new services.

SIP devices can receive service from a SIP proxy as the endpoint places a call, as a call arrives, or during the middle of a call. There is no defined way within SIP of providing services via a web browser or a feature server, as everything is done within the context of a "session".

Video and Data Conferencing
H.323 fully supports video and data conferencing. Procedures are in place to provide control for the conference as well as lip synchronization of audio and video streams.

SIP has limited support for video and no support for data conferencing protocols like T.120. SIP has no protocol to control the conference and there is no mechanism within SIP for lip synchronization. There is no standard means of recovering from packet loss in a video stream (to parallel H.323's "video fast update" command).

Administrative Requirements
H.323 does not require a gatekeeper. A call can be made directly between two endpoints.
However, most devices do utilize a gatekeeper for the purpose of registration and address resolution

SIP does not require a proxy. A call can be made directly between two user agents.
However, most devices do utilize a SIP proxy for the purpose of registration, address resolution, and call routing.


Codecs
H.323 supports any codec, standardized or proprietary. No registration authority is required to use any codec in H.323.

SIP supports any IANA-registered codec (as a legacy feature) or other codec whose name is mutually agreed upon.


Firewall/NAT support
Provided by H.323 "proxy" or by the endpoint, both in conjunction with a gatekeeper residing in the public network. Refer to H.460.17, H.460.18, and H.460.19.

SIP does not defined a NAT/FW traversal mechanism, as this is left to other standard. Some standards that have been defined or are being defined are STUN, TURN, ANAT, and ICE. (All of this has been work in progress for years, with most workable solutions done by agreed convention.)


Transport protocol
H.323 Reliable or unreliable, e.g., TCP or UDP. Most H.323 entities use a reliable transport for signaling.

SIP Reliable or unreliable, e.g., TCP or UDP. Most SIP entities use an unreliable transport for signaling.


Third-party Call Control
H.323 ->Yes, through third-party pause and re-routing which is defined within H.323. More sophisticated control is defined by the related H.450.x series of standards.

SIP->Yes, through SIP as described in RFC 3


Conferencing Entity
H.323-Yes, an MC is required for this, but it could be co-located in a participating endpoint, or all endpoints could contain an MC. A stand-alone conference bride may provide this functionality and H.323 has well-defined procedures for such entities.

SIP-No; however, SIP user agents may perform conferencing themselves. A stand-alone conference bridge may also provide this functionality


Authentication
H 323 - Yes, via H.235.

SIP-Yes, via HTTP (Digest and Basic), SSL, PGP, S/MIME, or various other means.


DTMF Carriage
H323 - Three ways, with the alphanumeric choice of the H.245 UserInputIndication message being the baseline carriage common to all H.323 endpoints

SIP- Three ways. There is no baseline carriage, which presents issues of interoperability. However, transport of DTMF via the INFO method and RFC 2833 are most common.

Cisco CCNP Exam (640-604) Simulator 4.0.0

Ensure your success in Cisco CCNP exam (640-604) with Whizlabs simulator, the most effective training software for the Cisco certification exams. Developed by highly experienced and certified professionals, it offers 5 mock exams (280 questions) on the latest pattern in a simulated environment.Last but not the least; it comes with FREE technical support and "Unconditional 100% Money Back Guarantee". Check out the FREE demo version. System Requirements 32 MB RAM, 20 MB HD Space,Internet Explorer (5 or above) What's new New test engine, Updated content


Download :

http://software.filefactory.com/Windows/Whizlabs_Cisco_CCNP_Exam_640-604_Simulator_4-0-0/Download.html

WinAgents RouterTweak 1.0.136.0

WinAgents RouterTweak is a specialized terminal shell making it easier to control the configuration of routers, switches and firewalls from the Cisco Systems company

Knowing the principles of working with the command line interface of Cisco devices, you can use WinAgents RouterTweak to automate the most common tasks of network device administration. This approach saves your time by allowing you to hand over routine operations to the program. Here are some benefits you get by using WinAgents RouterTweak:

Reducing the time needed to connect to a device. Having specified the username and password for connecting to a device only once, you will not have to spend time on entering them again when you connect to your router next time. WinAgents RouterTweak will enter the account data itself and switch to the privileged mode if necessary. Viewing the configuration of a device in a convenient form. Just click once to get the configuration of your device in a visual form. Syntax highlighting and the structure tree of the device configuration will allow you to quicker find your bearings among numerous configuration commands.

Increasing the speed of work with access control lists (ACL). WinAgents RouterTweak allows you to do without a TFTP server while editing access control lists. You can add, edit and remove commands located in the middle of ACLs. The program knows about the peculiarities of using the command line interface with Cisco access control lists and takes them into account while editing ACLs.

Usability in editing the configuration of devices. It is easier to edit configuration commands due to the context help system. While you are adding a new command to the configuration file, WinAgents RouterTweak requests its possible parameters from the device. In the process of editing commands, you see the list of available variants for each command all the time and can select one of them without entering the entire string.

Download :

http://software.filefactory.com/Windows/WinAgents_RouterTweak_1-0-136-0/Download.html

File Size
3.43 MB

VoIP Hacks Tips and Tools

VoIP is simply overflowing with hack potential, and VoIP Hacks is the practical guide from O'Reilly that presents these possibilities to you. It provides dozens of hands-on projects for building a VoIP network, showing you how to tweak and customize a multitude of exciting things to get the job done. Along the way, you'll also learn which standards and practices work best for your particular environment. Among the quick and clever solutions showcased in the book are those for:

gauging VoIP readiness on an enterprise network

*using SIP, H.323, and other signaling specifications
*providing low-layer security in a VoIP environment
*employing IP hardphones, analog telephone adapters, and softPBX servers
*dealing with and avoiding the most common VoIP deployment mistakes

Download :

http://rapidshare.com/files/3934671/VoIP.Hacks.Tips._.Tools.for.Internet.Telephony-OReilly.rar

Cisco: A Beginner's Guide, Fourth Edition

TITLE : Cisco: A Beginner's Guide, Fourth Edition (Beginner's Guide (Osborne Mcgraw Hill)) (Paperback)

AUTHOR : by Toby Velte (Author), Anthony Velte (Author)

PUBLISHER : McGraw-Hill Osborne Media publisher

ISBN : 0072263830

EDITION : 4th

PUB DATE : November 17, 2006

LANGUAGE : English

RLS DATE : 04/26/2007

BBLFORMAT : CHM SIZE : 11 x 2.88 MB

Here is a fully updated edition of the bestselling introductory guide to Cisco products and technologies. Cisco: A Beginner's Guide, Fourth Edition provides you with a practical hands-on resource for successfully designing and managing a Cisco network. Learn to work with Cisco routers and switches, wireless technologies, and storage tools. You'll also get full details on network security, including firewalls, as well as communications solutions such as VoIP. This is a must-have resource for anyone interested in internetworking and Cisco technologies.

- Work with Cisco's Internet technologies

- Configure Cisco routers and networks

- Understand Cisco internetworking technologies including LAN switches, multilayered switching, and VLANs

- Secure your network using CiscoSecure ACS, Cisco PIX firewall, IOS Firewall, and other methods

- Enable wireless internetworking using the Cisco Aironet and Airespace products

- Deploy VoIP via Cisco Unified Communications

- Implement Cisco storage area network (SAN) and content delivery network (CDN) solutions

- Use both open standard routing protocols (RIP, OSPF, BGP) and Cisco-proprietary protocols (IGRP and EIGRP)

- Design, manage, and troubleshoot a robust Cisco network

Download:

Code: http://depositfiles.com/files/805958

http://rapidshare.com/files/28266821/0072263830.zip

CBT Cisco CCNA Vol.1 - Vol.3 CD

CBT Cisco CCNA Vol.1 - Vol.3 CD 810 MB
--------------------------------------------

The CCNA certification (Cisco Certified Network Associate) indicates a foundation in and apprentice knowledge of networking. CCNA certified professionals can install, configure, and operate LAN, WAN, and dial access services for small and medium networks, including but not limited to use of these protocols: IP, IGRP, Serial, Frame Relay, IP RIP, VLANs, RIP, Ethernet, Access Lists.
All courses are distributed on CD-ROM so there is no need for an internet connection. Just install the courses to your personal computer or laptop and let the learning begin. All trainers are certified professionals with an average of 8-12 years of experience in their field.

Download:

http://www.filefactory.com/file/c709bd

Download CertExams Router Simulator 3.0

Provides lab exercises and Cisco IOS router console simulation with advanced features like RIP, EIGRP, OSPF routing, telnet, and ping support. Lab exercises -currently 40+ labs are included. Router console simulator Simulate up to 3 Cisco® IOS routers 60+ router commands supported Labs for 1900 and 2950 switches included Detailed help files The router labs made available in the Router Simulator are given below. Please note that we add and/modify the labs from time to time. Available Labs 1.0 Switch Fundamentals: 1.1 switch 1900 password assignment 1.2 switch 2950 console password assignment 1.3 switch 2950 vty password assignment 1.4 switch 2950 setting privileged EXE password 1.5 2950 enable interface 1.6 Basic switch interface configuration 2.0 IOS Fundamentals Lab 2.1 Logging to the router 2.2 Router banner MOTD 2.3 Setting host name 2.4 Interface configuration 2.5 Setting bandwidth 2.6 Setting console password 2.7 Setting telnet password 2.8 Copy active configuration 2.9 CDP configuration 2.10 Show CDP 2.11 Show CDP neighbors 2.12 Shutdown an interface 2.13 Set keepalive 2.14 Show commands 2.15 Setting password 2.16 Setting Hostname and Banner 2.17 Configuring Router Console and Line Passwords 3.0 Switch Configuration and VLAN 3.1 Basic switch IP configuration 3.2 Troubleshooting 1900 series switch 3.3 Configuring 2950 series switch 3.4 Troubleshooting 2950 switch 3.5 Configuring VLANs on 1900 and 2950 switches 4.0 Access Lists 4.1 Creating access-list 4.2 Applying access-list to an interface 4.3 View access-list entries 4.4 Standard access-lists: Scenario lab 1 4.5 Standard access-lists: Scenario lab 2 4.6 Extended access-lists: Scenario lab 1 4.7 Router Access-List Configuration 5.0 Routing Fundamentals Labs 5.1 Configuring RIP 5.2 Configuring static routes 5.3 Configuring default routes 5.4 Viewing IP RIP information 5.5 Basic IGRP routing 6.0 Wide Area Networking 6.1 PPP configuration

Download :

http://rapidshare.de/files/23870647/RoutSim.rarhttp://depositfiles.com/files/322272

Password/Crack CCNA

Router Troubleshooting 2

Q.You want to clear an old configuration out of your router and return it to a factory default configuration.

Ans.You can delete the current startup configuration files and return the router to its factory default settings with the erase nvram: command:

Router1#erase nvram:
Erasing the nvram filesystem will remove all files! Continue? [confirm]
[OK]
Erase of nvram: complete
Router1#reload
System configuration has been modified. Save? [yes/no]: no
Proceed with reload? [confirm]
You can achieve the same result with the erase startup-config command:
Router1#erase startup-config
Erasing the nvram filesystem will remove all files! Continue? [confirm]
[OK]
Erase of nvram: complete
Router1#reload
Proceed with reload? [confirm]

Q.You want to upgrade the IOS image that your router uses.

Ans. The copy tftp command allows you to use TFTP to download a new IOS version into the router's Flash memory:

Router1#copy flash:
Destination filename [c2600-ik9o3s-mz.122-12a.bin]?
Accessing ..
Erase flash: before copying? [confirm]
Erasing the flash filesystem will remove all files! Continue? [confirm]
Erasing
device... eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee ...
erased
Erase of flash: complete
Loading c2600-ik9o3s-mz.122-12a.bin from 172.25.1.1 (via Fastethernet0/0.1): !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!![OK - 11135588 bytes]
Verifying checksum... OK (0xE643)
11135588 bytes copied in 82.236 secs (135410 bytes/sec)
Router1# reload
Proceed with reload? [confirm]

Q.You want to save a backup copy of your IOS image on a TFTP server.

Ans. You can upload a copy of your router's IOS image to a TFTP server with the following set of commands:

Freebsd% touch /tftpboot/c2600-ik9o3s-mz.122-12a.bin
Freebsd% chmod 666 /tftpboot/c2600-ik9o3s-mz.122-12a.bin
Freebsd% telnet Router1
Trying 172.25.1.5...
Connected to Router1.Escape character is '^]'.
User Access Verification
Password:
Router1>enPassword:
Router1#copy flash:c2600-ik9o3s-mz.122-12a.bin tftp
Address or name of remote host [ ]? 172.25.1.1
Destination filename [c2600-ik9o3s-mz.122-12a.bin]? !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!11135588 bytes copied in 52.588 secs (211752 bytes/sec)
Router1#

Q.You want to load an IOS image into your router through a serial connection to the console or AUX ports.

Ans. You can use the following set of commands to copy an IOS image onto a router through the console or the AUX port:

Router1#copy xmodem: slot1:
**** WARNING ****
x/ymodem is a slow transfer protocol limited to the current speedsettings of the auxiliary/console ports. The use of the auxilaryport for this download is strongly recommended.During the course of the download no exec input/output will be available.
---- ******* ----
Proceed? [confirm]
Destination filename [ ]? c3620-ik9s-mz.122-12a.bin
Erase slot1: before copying? [confirm]
Use crc block checksumming? [confirm]
Max Retry Count [10]:
Perform image validation checks? [confirm]
Xmodem download using crc checksumming with image validationContinue? [confirm]
Ready to receive file...........CC
4294967295 bytes copied in 1450.848 secs (1271445669961 bytes/sec)
Router1#

Q.You want to configure and monitor your router using a browser interface.

Ans. Cisco includes an HTTP server in the IOS. You can enable this feature on a router and then use any standard web browser instead of Telnet to access the router:

Router1#configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
Router1(config)#access-list 75 permit 172.25.1.1
Router1(config)#access-list 75 deny any
Router1(config)#ip http server
Router1(config)#ip http access-class 75
Router1(config)#end
Router1#

Q.You want to set the router to automatically reload at a specified time.

Ans.You can set the router to reload after waiting a particular length of time with the reload in command:

Router1#reload in 20
Reload scheduled for 11:33:53 EST Sat Feb 1 2003 (in 20 minutes)
Proceed with reload? [confirm]
Router1#
The reload at command lets you specify a particular time and date when you want the router to reload:
Router1#reload at 14:00 Feb 2
Reload scheduled for 14:00:00 EST Sun Feb 2 2003 (in 26 hours and 44 minutes)
Proceed with reload? [confirm]
Router1#

Router Troubleshooting

Q.Restore the Cisco IOS to a router

Ans.Have you ever accidentally wiped out the IOS on your router? If you're working quickly and not paying attention, it can be an easy mistake to make. All it takes is making a typo in the destination filename when you're trying to save a change.
Here's an example:

router# copy running-config startp-config
Destination filename [startp-config]?
Erase flash: before copying? [confirm]
Erasing the flash filesystem will remove all files! Continue? [confirm]Hitting [Enter] a couple of times out of habit can all too quickly wipe out the IOS. If you don't realize the mistake in time, rebooting the router means the IOS is gone for good, and the router won't boot up.

Losing the IOS can also happen when upgrading the flash on the router. As the Cisco IOS grows larger, having to upgrade your flash is a very common task. But when you install the new flash, it has no IOS, leaving you in the same position as if you had accidentally erased the flash.


Unfortunately, if you're like many people, when you wipe out the IOS, you may not have a backup copy of the IOS. Or, you may not have access to the Cisco IOS download site or have the time to download the somewhat large IOS file.

And if you're looking for the same IOS on all of your routers, it can be difficult to locate it on the Cisco IOS download site. Many times, it's much easier to take the IOS from an existing router and restore it on the router that's missing its IOS.

Let's look at the step-by-step process for restoring the Cisco IOS to a router using this method.

Install a TFTP server

First you need to install a (TFTP) server. I recommend the Tftpd32 server, which you can download from the Web. This is a great TFTP server, without a lot of the fluff that most of the others have. At less than 1 MB, it's very small and has no install application.


Run the TFTP server on a PC

If you've just pulled the working router off a shelf, you can connect the PC to the router with a reverse Ethernet cable. Configure the router and PC on the same network. Make sure that you can ping the router and that the router can ping you.

If your working router is up on your network, you can just download the IOS over the network directly using instructions in the next section

Copy the IOS from the working router to the PC
Here's an example of how to accomplish this:

copy c2600-12-3.xxxx.bin tftp://10.253.15.72 Replace 10.253.15.72 with the IP address of your PC, and replace c2600 with the name of your IOS. (You can locate the name of the IOS on the working router using the show flash command.)

This saves the IOS on the PC in the directory configured by the TFTP server. Figure A shows an example of what it looks like while downloading. Make sure to note the directory in which you'll save the IOS.

Download the IOS to the nonworking router

The best way to accomplish this is via Ethernet. The alternative—using XMODEM through the console—will be very slow, even if you increase the serial port baud rate to the maximum. So, instead, connect the PC's reverse Ethernet cable to the nonworking router (or use two normal/straight-through Ethernet cables and a switch).

Without an IOS, the nonworking router will boot up in ROMmon mode. The prompt will look like this:

rommon>Verify the necessary settings

On the console of the nonworking router while in ROMmon mode, use the set command to display the current settings, which the program will use to download the IOS via TFTP. (For a Cisco example of these steps, check out this Cisco documentation.)

For example, here are the settings you must set for the tftpdnld command to work:

rommon> setIP_ADDRESS=10.253.100.126
IP_SUBNET_MASK=255.255.0.0
TFTP_SERVER=10.253.15.72
DEFAULT_GATEWAY=10.253.1.1
TFTP_FILE={the name of the IOS that is saved on the PC}
However, your settings may not contain any of the required variables for the tftpdnld command. By default, it may look something like this:

rommon 9 > set
PS1=rommon ! >
BSI=0
RET_2_RUTC=0
RET_2_RTS=?=1
If this is the case, set the required variables. While it might seem obvious to use the set command to set the variables, you can actually set the variables simply by entering the name of the variable, the equal sign [=], and the value.

For example, to set the IP address of the broken router, you would use the following:For example, to set the IP address of the broken router, you would use the following:

IP_ADDRESS=10.253.100.126Final steps

After setting your values, run the tftpdnld command, which will replace the IOS. Listing A provides an example of how I restored a router

An alternate approach to the tftpdnld command

However, if the tftpdnld command doesn't work for some reason, you can use the xmodem command to send the IOS over the serial console line. (For instructions for this process, check out this Cisco documentation.) However, if you decide to take this route, it's a good idea to change the baud rate on the console and your PC to 115,200 so it doesn't take more than four hours for an 8-MB IOS file to transfer over the 9600-baud console.

On a final note, keep in mind that different models of Cisco routers and different Cisco firmware versions respond differently. For example, these commands performed on a 2600 series router may not work on a 3600 series router. However, the basic process remains the same

Q.You want to load configuration commands via the Trivial File Transfer Protocol (TFTP).

Ans. You can use the copy tftp: command to configure the router via the TFTP:
Router1#copy tftp://172.25.1.1/NEWCONFIG
running-configDestination filename [running-config]?
Accessing tftp://172.25.1.1/NEWCONFIG...
Loading NEWCONFIG from 172.25.1.1 (via FastEthernet0/0.1): !
[OK - 24 bytes] 24 bytes copied in 0.192 secs (125 bytes/sec)
Router1#


Q,You want to store a backup copy of your router's configuration on a TFTP server.
Ans. This example shows how to use TFTP to upload a copy of the router's active configuration to a remote server:
router#telnet Router1
Trying 172.25.1.5...
Connected to Router1.Escape character is '^]'.
User Access Verification
Password:
Router1>enPassword:
Router1#copy running-config tftp://172.25.1.1/router1-confg
Address or name of remote host [172.25.1.1]? Destination filename [router1-confg]? !!!9640 bytes copied in 3.956 secs (2437 bytes/sec)
Router1#


Q.You want to boot the router using an alternate configuration.

Ans. The following set of commands allows you to automatically load a configuration file located on a remote TFTP server when the router boots:
Router1#configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
Router1(config)#service config
Router1(config)#boot network tftp Network-auto 172.25.1.1
Router1(config)#boot host tftp Router8-auto 172.25.1.1
Router1(config)#end
Router1#

Q.Your configuration file has become larger than the router's available NVRAM.

Ans.You can compress your router's configuration file before saving it to NVRAM to allow you to save more configuration information. The command service compress-config will compress the configuration information when the router saves the file, and uncompress it when it is required:
Router1#configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
Router1(config)#service compress-config
Router1(config)#end
Router1#

ISDN Message Codes

Decimal Value
Hex Value
Cause
Diagnostics
Explanation
--------------------------------------------------------------------------------------

1
01
Unallocated (unassigned) number
Note 10
The ISDN number was sent to the switch in the correct format; however, the number is not assigned to any destination equipment.




2
02
No route to specified transit network
Transit network identity (Note 9)
The ISDN exchange is asked to route the call through an unrecognized intermediate network.




3
03
No route to destination
Note 10
The call was routed through an intermediate network that does not serve the destination address.




6
06
Channel unacceptable

The service quality of the specified channel is insufficient to accept the connection.






7
07
Call awarded and being delivered in an established channel

The user is assigned an incoming call that is being connected to an already-established call channel.






16
10
Normal call clearing
Note 10
Normal call clearing has occurred.






17
11
User busy

The called system acknowledges the connection request but is unable to accept the call because all B channels are in use.






18
12
No user responding

The connection cannot be completed because the destination does not respond to the call.






19
13
No answer from user (user alerted)

The destination responds to the connection request but fails to complete the connection within the prescribed time. The problem is at the remote end of the connection.






21
15
Call rejected
Note 10. User supplied diagnostic (Note 4)
The destination is capable of accepting the call but rejected the call for an unknown reason.






22
16
Number changed

The ISDN number used to set up the call is not assigned to any system.






26
1A
Non-selected user clearing

The destination is capable of accepting the call but rejected the call because it was not assigned to the user.






27
1B
Designation out of order

The destination cannot be reached because the interface is not functioning correctly, and a signaling message cannot be delivered. This might be a temporary condition, but it could last for an extended period of time. For example, the remote equipment might be turned off.






28
1C
Invalid number format

The connection could be established because the destination address was presented in an unrecognizable format or because the destination address was incomplete.






29
1D
Facility rejected
Facility identification (Note 1)
The facility requested by the user cannot be provided by the network.






30
1E
Response to STATUS ENQUIRY

The status message was generated in direct response to the prior receipt of a status enquiry message.






31
1F
Normal, unspecified

Reports the occurrence of a normal event when no standard cause applies. No action required.






34
22
No circuit/channel available

The connection cannot be established because no appropriate channel is available to take the call.






38
26
Network out of order

The destination cannot be reached because the network is not functioning correctly, and the condition might last for an extended period of time. An immediate reconnect attempt will probably be unsuccessful.






41
29
Temporary failure

An error occurred because the network is not functioning correctly. The problem will be resolved shortly.






42
2A
Switching equipment congestion

The destination cannot be reached because the network switching equipment is temporarily overloaded.






43
2B
Access information discarded
Discarded information element identifier(s) (Note 5)
The network cannot provide the requested access information.






44
2C
Requested circuit/channel not available

The remote equipment cannot provide the requested channel for an unknown reason. This might be a temporary problem.






47
2F
Resources unavailable, unspecified

The requested channel or service is unavailable for an unknown reason. This might be a temporary problem.






49
31
Quality of service unavailable
Table B-2
The requested quality of service cannot be provided by the network. This might be a subscription problem.






50
32
Requested facility not subscribed
Facility identification (Note 1)
The remote equipment supports the requested supplementary service by subscription only.






57
39
Bearer capability not authorized
Note 3
The user requested a bearer capability that the network provides, but the user is not authorized to use it. This might be a subscription problem.






58
3A
Bearer capability not presently available
Note 3
The network normally provides the requested bearer capability, but it is unavailable at the present time. This might be due to a temporary network problem or to a subscription problem.






63
3F
Service or option not available, unspecified

The network or remote equipment was unable to provide the requested service option for an unspecified reason. This might be a subscription problem.






65
41
Bearer capability not implemented
Note 3
The network cannot provide the bearer capability requested by the user.






66
42
Channel type not implemented
Channel Type (Note 6)
The network or the destination equipment does not support the requested channel type.






69
45
Requested facility not implemented
Facility Identification (Note 1)
The remote equipment does not support the requested supplementary service.






70
46
Only restricted digital information bearer capability is available

The network is unable to provide unrestricted digital information bearer capability.






79
4F
Service or option not implemented, unspecified

The network or remote equipment is unable to provide the requested service option for an unspecified reason. This might be a subscription problem.






81
51
Invalid call reference value

The remote equipment received a call with a call reference that is not currently in use on the user-network interface.






82
52
Identified channel does not exist
Channel identity
The receiving equipment is requested to use a channel that is not activated on the interface for calls.






83
53
A suspended call exists, but this call identity does not

The network received a call resume request. The call resume request contained a Call Identify information element that indicates that the call identity is being used for a suspended call.






84
54
Call identity in use

The network received a call resume request. The call resume request contained a Call Identify information element that indicates that it is in use for a suspended call.






85
55
No call suspended

The network received a call resume request when there was not a suspended call pending. This might be a transient error that will be resolved by successive call retries.






86
56
Call having the requested call identity has been cleared
Clearing cause
The network received a call resume request. The call resume request contained a Call Identity information element, which once indicated a suspended call. However, the suspended call was cleared either by timeout or by the remote user.






88
58
Incompatible destination
Incompatible parameter (Note 2)
Indicates that an attempt was made to connect to non-ISDN equipment. For example, to an analog line.






91
5B
Invalid transit network selection

The ISDN exchange was asked to route the call through an unrecognized intermediate network.






95
5F
Invalid message, unspecified

An invalid message was received, and no standard cause applies. This is usually due to a D-channel error. If this error occurs systematically, report it to your ISDN service provider.






96
60
Mandatory information element is missing
Information element identifier(s) (Note 5)
The receiving equipment received a message that did not include one of the mandatory information elements. This is usually due to a D-channel error. If this error occurs systematically, report it to your ISDN service provider.






97
61
Message type non-existent or not implemented
Message type
The receiving equipment received an unrecognized message, either because the message type was invalid or because the message type was valid but not supported. The cause is due to either a problem with the remote configuration or a problem with the local D channel.






98
62
Message not compatible with call state or message type non-existent or not implemented
Message type
The remote equipment received an invalid message, and no standard cause applies. This cause is due to a D-channel error. If this error occurs systematically, report it to your ISDN service provider.






99
63
Information element non-existent or not implemented
Information element identifier(s) (Notes 5, 7)
The remote equipment received a message that includes information elements, which were not recognized. This is usually due to a D-channel error. If this error occurs systematically, report it to your ISDN service provider.






100
64
Invalid information element contents
Information element identifier(s) (Note 5)
The remote equipment received a message that includes invalid information in the information element. This is usually due to a D-channel error.






101
65
Message not compatible with call state
Message type
The remote equipment received an unexpected message that does not correspond to the current state of the connection. This is usually due to a D-channel error.






102
66
Recovery on timer expires
Timer number (Note 8)
An error-handling (recovery) procedure was initiated by a timer expiry. This is usually a temporary problem.






111
6F
Protocol error, unspecified

An unspecified D-channel error when no other standard cause applies.






127
7F
Internetworking, unspecified

An event occurred, but the network does not provide causes for the action that it takes. The precise problem is unknown.

Deploying Cisco Voice over IP Solutions

Book Description:
============

Learn real-world voice-over-IP deployment solutions and strategies from the Cisco experts
Deploying Cisco Voice over IP Solutions covers:

Definitive guidelines on real-world VoIP deployments, the fundamentals of the latest VoIP solutions, and a look into the future of VoIP services

Different techniques for engineering and properly sizing traffic-sensitive voice networks

Basic concepts applicable to echo analysis, echo cancellation, and locating and eliminating echoes

Various QoS features applicable to voice

Detailed information on call admission control (CAC)

Dial plan configuration recommendations on Cisco H.323 gateways and gatekeepers used to support large dial plans

Basic tasks of designing a long-distance VoIP network

The two classes of hosted voice networks: Managed Multiservice (MMS) networks and packet voice VPNs

Fax services store and forward as well as real-time relay fax services

Sample configurations and step-by-step examples to help you learn how to build a VoIP network

Deploying Cisco Voice over IP Solutions provides networking professionals the knowledge,
advice, and insight necessary to design and deploy voice over IP (VoIP) networks that meet customers' needs for scalability, services, and security. Beginning with an introduction to the important preliminary design elements that need to be considered before implementing VoIP, Deploying Cisco Voice over IP Solutions also demonstrates the basic tasks involved in designing an effective service provider-based VoIP network. You'll conclude with design and implementation guidelines for some of the more popular and widely requested VoIP services, such as prepaid services, fax services, and virtual private networks (VPNs).

This book is a collaboration of Cisco Systems CCIE(r) engineers, technical marketing engineers, and systems engineers. You'll find design experience from people who have designed some of the world's largest VoIP networks.

Download :

http://rapidshare.com/files/12112950/1587050307.zip