Posts Tagged ‘CCIE Bootcamps’

Automating Dial Backup

February 11th, 2012   by Daniel

This recipe includes several important features. First, notice that we have configured dial backup using an ISDN BRI interface on this router. So we have to set up the ISDN configuration:

Router1(config)#interface BRI0/0
Router1(config-if)#isdn switch-type basic-ni
Router1(config-if)#isdn spid1 800555123400 5551234
Router1(config-if)#isdn spid2 800555123500 5551235

This site is connected to a National ISDN switch. So we have defined the switch type to be basic-ni. If this had been a PRI rather than a BRI, we would have used primary-ni. And because it is a National ISDN switch, we also have to include the ISDN Service Profile Identifier (SPID) values. These define the telephone numbers associated with each of the two B channels in the BRI. Note that the syntax includes essentially the same number twice:

Router1(config-if)#isdn spid1 800555123400 5551234

The first argument is the whole telephone number including area code with 00 tacked on the end. These extra two digits vary between different telephone companies. Sometimes this needs to be a different code, such as 0101. The telephone company can tell you the correct value to include.

The second number is not always required. This is essentially the phone number that you would need to call this B channel from the other B channel. In this example, the telephone company uses seven-digit local dialing, so we can eliminate the area code.

There are several different kinds of ISDN switches, and it's important to find out what your carrier uses to ensure that you configure the router properly.

For telephone companies that use AT&T switches:

Router1(config-if)#isdn switch-type basic-5ess

For telephone companies that use Nortel DMS100 switches:

Router1(config-if)#isdn switch-type basic-dms100

Telephone companies outside of North America often use different kinds of ISDN switches. In France you would use the following command:

Router1(config-if)#isdn switch-type vn3

In Australia, the telephone company uses TS013 ISDN switches:

Router1(config-if)#isdn switch-type basic-ts013

In Norway and New Zealand:

Router1(config-if)#isdn switch-type basic-net3

In Germany:

Router1(config-if)#isdn switch-type basic-1tr6

And, in Japan:

Router1(config-if)#isdn switch-type ntt

Please contact the local telephone company supplying the BRI circuit to ensure that you have the right switch type. And be sure to ask them whether you need to configure SPIDs on your router. Some switches require them; others don't.

You can verify that you have your ISDN configuration working correctly with the show isdn status command:

Router1#show isdn status
Global ISDN Switchtype = basic-ni
ISDN BRI1/0 interface
    dsl 8, interface ISDN Switchtype = basic-ni
    Layer 1 Status:
    ACTIVE
    Layer 2 Status:
    TEI = 85, Ces = 1, SAPI = 0, State = MULTIPLE_FRAME_ESTABLISHED
    TEI = 86, Ces = 2, SAPI = 0, State = MULTIPLE_FRAME_ESTABLISHED
    TEI 85, ces = 1, state = 8(established)
        spid1 configured, spid1 sent, spid1 valid
    TEI 86, ces = 2, state = 8(established)
        spid2 configured, spid2 sent, spid2 valid
    Layer 3 Status:
    0 Active Layer 3 Call(s)
    Activated dsl 8 CCBs = 0
    The Free Channel Mask:  0x80000003
Total Allocated ISDN CCBs = 2
Router1#

In this case, you can see you have an "active" status at Layer 1, and both of the Terminal Endpoint Identifiers (TEI) are in a "MULTIPLE_FRAME_ESTABLISHED" state. This means that the router is talking with the telephone company's ISDN switch, and that both of the B channels are ready to go. This display also says that there are currently no active calls at Layer 3. As an aside, we should point out that this refers to the ISDN circuit's Layer 3, and not the IP network layer. When the router places a call, it will establish a PPP connection, which will support IP.

The actual dialing is done by the dialer map command:

Router1(config)#dialer-list 1 protocol ip list 101
Router1(config)#access-list 101 deny eigrp any any
Router1(config)#access-list 101 permit ip any any
Router1(config)#interface BRI0/0
Router1(config-if)#dialer map ip 10.1.99.1 name dialhost broadcast 95551212
Router1(config-if)#dialer-group 1

In this case, the dialer map says that to reach the IP address 10.1.99.1, it should dial the phone number 95551212 to reach the router called dialhost. Note that we have included a "9" at the start of this phone number. Again, you will need to ask your local telephone company whether there is a special code digit. We have seen places where we needed a 9, an 8, or nothing at all.

The broadcast keyword in this command allows both multicast and broadcast traffic to use this dialup link. This is extremely important for routing protocols such as EIGRP, RIPv2, and OSPF, which use multicasts for sending their updates between routers. This example uses EIGRP, so we need to include this keyword.

With this type of dialer configuration, you also need to define a dialer group. In this case, we have assigned this interface to dialer group number 1. You configure the behavior of this dialer group with the dialer-list statement, which defines what an interesting packet is for this network.

An interesting packet is one that will bring up the dialer, or keep it active if it is already up. If the circuit is up, then the router will reset the idle timer every time it sees an interesting packet. The result is that as long as there are interesting packets to send, the router will keep the dial session active. Otherwise, it will disconnect the call when the idle timer expires. This is particularly important when you are calling long distance numbers. If the wrong packets are considered interesting, it could mean an expensive phone bill.

So we have associated the dialer list with an access list that specifies what is interesting. In this case, all IP packets except EIGRP are interesting. It's important to remember that EIGRP packets will still pass through the dial link normally. But if the link is not active, an EIGRP packet is not sufficient to bring it up. And if the link is active, the presence of EIGRP packets alone won't prevent the router from dropping it.

However, sometimes you do want the link to remain active all the time. For example, the administrators of some small WANs like to keep ISDN sessions nailed up all the time (usually because they only pay an access charge, and not a usage or long distance charge). So if the session drops for any reasons, they want it to immediately dial up again. In this case, you could replace the access list with a new one that finds all traffic interesting:

Router1(config)#access-list 101 permit ip any any

It's easier still if you modify the dialer-list command to make all IP traffic interesting:

Router1(config)#dialer-list 1 protocol ip permit

When the router dials, it will use Point-to-Point Protocol (PPP) to carry Layer 3 protocols such as IP. So you need to define several PPP parameters:

Router1(config)#interface BRI0/0
Router1(config-if)#encapsulation ppp
Router1(config-if)#ppp authentication chap
Router1(config-if)#exit
Router1(config)#username dialhost password dialpassword

The encapsulation command simply tells the router to use PPP as its Layer 2 protocol. But because you don't want just anybody dialing into this dialhost router, it's a good idea to include some authentication. In this case, we have configured the router to use Challenge Handshake Authentication Protocol (CHAP) for authenticating PPP sessions. This basically means that both this router and the router it dials to will exchange usernames and passwords when they connect. The username for this router is the router's name. And we define the username and password for the other router with the username command.

We note in passing that Cisco supports another PPP authentication scheme called Password Authentication Protocol (PAP). CHAP is much more secure because it only passes passwords in encrypted form rather than clear text, as PAP does. CHAP is no more complex to set up, and presents no appreciable extra load on the router's resources. So we strongly recommend using CHAP rather than PAP.

Because this is an ISDN BRI interface, we would like to be able to use both of the B channels to increase the available bandwidth:

Router1(config)#interface BRI0/0
Router1(config-if)#dialer load-threshold 50 either
Router1(config-if)#ppp multilink

The command ppp multilink means that this PPP session can be split across several physical connections. This feature allows full load balancing and packet sequencing across all of the connections in the multilink bundle. In this case, we want to bond the two ISDN B channels into a single 128 Kbps PPP link. By default, the router will use only one of these channels, whichever one is available. The dialer load-threshold command specifies the rule that the router will use to bring up the second link. In this case, we have specified that if the traffic utilization in either direction (input or output) reaches ~20 percent (50/255 link utilization), then the router should bring up the second channel.

We have also modified the default idle timeout:

Router1(config)#interface BRI0/0
Router1(config-if)#dialer idle-timeout 300

By default, the router will drop the dial session if there have been no interesting packets for 120 seconds. We have increased this value to 300 seconds. Because ISDN dials so quickly, this is not vital. But with asynchronous modem dialup, it can take up to a full minute to establish a new session. You often need to increase the idle timer is to make sure that the primary connection is up and stable before disconnecting the backup circuit. It is a good idea to wait for the routing protocol to converge, and to ensure that the primary circuit isn't simply bouncing up and down. You also have to trade off between the time required to establish a new session and the cost of any long distance charges on this line. We generally recommend using an idle timeout period of 5 minutes, as shown in the example.

Finally, we come to one of the most important features of this configuration, the trigger condition. This router will dial whenever it has traffic to send to the IP address 10.1.99.1, which is the IP address of the dialhost router itself. User traffic will be directed to end devices such as servers, not to routers. The only way to bring up this dial interface is if this router needs to send an interesting packet to the dial router's IP address. This is where the floating static route comes in.

we discussed floating static routes. These are routes whose administrative distances are so high that any dynamically learned route to the same destination will be better. So the router will only install this static route if the dynamic routing protocol can't offer anything better:

Router1(config)#ip route 0.0.0.0 0.0.0.0 10.1.99.1 180

In this particular case the routing protocol is EIGRP, which has an administrative distance of 90 by default for all internal routes and 170 for external routes. So, by creating this static default route with a metric of 180, we ensure that the router will never use it if it has anything better.

The net result is that if the primary link fails, EIGRP will lose all of its routes. So the router will install the floating static route to handle any user data packets that it needs to transmit. Since this route points to the far end of the dial link, this forces the router to bring up the dial connection.

The nice thing about this way of triggering dial backup is that it is extremely robust. Anything that causes you to lose connectivity for any reason will trigger the dial backup.

which uses the backup interface method to trigger dial backup, with the floating static configuration, you have the advantage that the interface remains up but not connected when the primary circuit is working. I

And one of the most useful features of this type of trigger mechanism is that you can test the dial backup easily. If you look at the dialer list, you will see that all the router needs to initiate a dial session is to have a packet to send to the far end that matches the dialer list. So, in this particular example, you could easily bring up a dial session for testing by just logging into the remote router and pinging the IP address of the dial backup router:

Router1#ping 10.1.99.1
Post in CCIE Labs | No Comments »

sense of understanding. The CCIE labs variety

February 9th, 2012   by Daniel

Implementing CCIE, pros have an opportunity to determine by themselves throughout the field of networking. Only a few thousand persons are considered to very clear the CCIE exam. CCIE labs are perceived as to impart substantial phase of coaching ambiance, which functions as a substantial revenue for candidates.

CCIE examination entails two assessments, which can be a CCIE prepared check out and a CCIE lab exam. In order to try the lab examination, you have to distinct the prepared exam. In case you are not in a position to obvious the published examination the initial time, you might want to check out for any hundred and eighty days for retaking it. Soon after clearing the published take a look at, it truly is most reliable to make an try for that CCIE lab examination within 18 months. It you're not able to very clear the lab examination, then you definitely could re-try within 12 months along with a look at to take care of the published examination result legitimate.

It's got a time prohibit of two hours and it is carried out in several take a look at centers across the world. The subjects lined within the authored test rely on the specialization or track you end up picking. For services supplier, chances are you'll choose from groups like Cable, DSL, IP Telephony, Dial, Subject material content Networking, Optical, WAN switching, and Metro Ethernet. Just about every composed test is constructed around inside the beta kind at a worth of $50 USD.

The CCIE lab exam is exclusive in nature, as it can be an eight-hour test, which tests the ability on the applicant to configure and troubleshoot networking tools. Cisco has big degree of package in its CCIE labs to be used inside the lab exams. The blue print from the lab examination is obtainable on its internet site. The lab examination is just not on hand in any respect Pearson VUE or Prometric testing centers.

A average CCIE R&S lab examination contains a two-hour hassle-taking pictures section by which you are presented a collection of tickets for preconfigured networks throughout the CCIE labs. Be certain to have the ability to identify and resolve the faults. You can proceed towards the configuration part following you end the troubleshooting part.

A sound passing score is critical to attempt a CCIE Labs exam. Cisco uses the help of proctors to guage the candidates with the preliminary rounds in its CCIE labs located worldwide. Factors are awarded when a criterion is met and grading is carried out working with some computerized tools. The outcomes of a lab examination are mirrored inside of forty eight hours. A move/fail is projected within the end result and in case of a fail, the areas where you're lacking behind are talked about so as to put together properly earlier than a re-try.

Cisco stands out in the field of networking by providing a CCIE certification so that you can pursue your education as well as get acknowledged by a reputed organization. The CCIE lab examination can be utilized for a platform to challenge your capability in varied tracks provided by Cisco. Attempting a lab examination requires rigorous schooling and big sense of understanding. The CCIE labs style step one to your significant potential career.

Post in CCIE Labs | No Comments »

Manual RSVP Reservations

February 8th, 2012   by Daniel

In this example, we will assume that we have a host device, acting as the sender, with IP address 192.168.100.202 and a second host, acting as the receiver, with IP address 192.168.9.100. The first host is connected to FastEthernet0/0 Router1:

Router1#configure terminal
Enter configuration commands, one per line.  End with CNTL/Z.
Router1(config)#interface FastEthernet0/0
Router1(config-if)#ip address 192.168.100.21 255.255.255.0
Router1(config-if)#ip rsvp bandwidth 128 56
Router1(config-if)#exit
Router1(config)#interface Serial0/0
Router1(config-if)#no ip address
Router1(config-if)#encapsulation frame-relay
Router1(config-if)#fair-queue 64 256 37
Router1(config-if)#ip rsvp bandwidth
Router1(config-if)#exit
Router1(config)#interface Serial0/0.1 point-to-point
Router1(config-subif)#ip address 192.168.55.9 255.255.255.252
Router1(config-subif)#frame-relay interface-dlci 904
Router1(config-fr-dlci)#ip rsvp bandwidth 128 56
Router1(config-subif)#exit
Router1(config)#ip rsvp sender 192.168.9.100 192.168.100.202 UDP 1300 1300 192.168.100.202 FastEthernet0/0 55 1
Router1(config)#end
Router1#

The second host is connected to the Ethernet0/0 interface on Router4, which is several hops away:

Router4# configure terminal
Router4(config)#interface Ethernet0/0
Router4(config-if)#ip address 192.168.9.3 255.255.255.0
Router4(config-if)#ip rsvp bandwidth 128 56
Router4(config-if)#exit
Router4(config)#interface Serial0/0
Router4(config-if)#no ip address
Router4(config-if)#encapsulation frame-relay
Router4(config-if)#fair-queue 64 256 37
Router4(config-if)#ip rsvp bandwidth
Router4(config-if)#exit
Router4(config)#interface Serial0/0.1 point-to-point
Router4(config-subif)#ip address 192.168.56.5 255.255.255.252
Router4(config-subif)#frame-relay interface-dlci 107
Router4(config-fr-dlci)#ip rsvp bandwidth 128 56
Router4(config-subif)#exit
Router4(config)#ip rsvp reservation 192.168.9.100 192.168.100.202 UDP 1300 1300 192.168.9.100 Ethernet0/0 FF RATE 55 1
Router4(config)#end
Router4#

It is worthwhile to review how RSVP works before looking at the mechanics of this recipe. A host that wants to send a data stream to a particular destination address or multicast group first makes an RSVP request to its first-hop router. This request asks for a particular set of QoS parameters, such as application bandwidth requirements, and specifies the destination IP address. Each router decides whether it can meet the requirement, accepting or rejecting the reservation. They then make the same request of the next hop router along the path to the destination. Once all of the routers between the source and destination have reserved the appropriate resources, the original host can begin transmitting application data, using the reserved resources along the entire data path.

The method is identical for unicast and multicast reservation requests, with each router relaying the request to a downstream peer until all of the destinations have been reached. Note that RSVP is inherently unidirectional. That is, it requests resources for sending data from a particular source to a particular destination or multicast group. If you want to reserve network resources to support a two-way unicast application, both the sender and the receiver must separately initiate requests.

RESV and PATH messages

There are two general message types in RSVP, PATH, and RESV. The initial request begins with a PATH message. The PATH message describes the specific flow that will use this reservation. So it includes the source and destination IP addresses, as well as the IP Protocol, such as TCP or UDP, and any port numbers. The PATH message also includes the requested average bit rate and burst size.

The PATH message is received by an upstream router, or perhaps the ultimate destination. If it is received by an intermediate router, this router must analyze the request and decide whether it can honor it. Ultimately, if the request is accepted, the router will create a new PATH message, requesting the same resource reservation from the next upstream router, but specifying itself as the source.

PATH messages always flow from the requester toward the destination.

RESV messages flow the opposite direction. The RESV CONFIRM messages describe the actual detailed bit rate and delay characteristics required to fulfill the PATH request. If an upstream router doesn't have the necessary resource to fulfill the request, it responds with an RESV ERROR message.

In Cisco router configuration, you can configure static PATH requests by using the ip rsvp sender and sender-host commands. And you can make static reservations, which will be described to upstream routers in RESV messages, using the ip rsvp reserveration and reservation-host commands. We will describe all of these commands below.

Two service types

There are two distinct types of service that a host can specify in an RSVP request. The first is called Controlled Load Service, which is specified in RFC 2211, and the second, called either Guaranteed Quality of Service or, more accurately, Guaranteed Bit Rate Service, is specified in RFC 2212.

Controlled Load Service, in a nutshell, means that the network behaves as if each segment were completely unloaded and therefore uncongested, but with bandwidth limited to the requested amount. Cisco routers implement this type of service by isolating the different flows and employing queuing mechanisms that mimic this type of response.

Guaranteed Bit Rate Service is somewhat more complicated. This service means that the network will mathematically guarantee the worst-case end-to-end queuing delay. There are two things to note about this description, however. First, it only guarantees the worst-case latency, not the average latency. The second is that, despite this, it is possible to make an estimate of the jitter, as this is governed by the worst-case latency. As long as the worst-case latency is small, then the jitter can be effectively minimized by employing small amounts of buffering on the end devices.

Controlled Load Service is well suited to many TCP applications, which tend to behave well until they encounter congestion and dropped packets. Conversely, Guaranteed Bit Rate Service tends to be a better choice for real-time voice and video applications.

The examples

Everything we have described so far implies that the source and destination host devices or applications are making the RSVP requests. However, this is not necessarily the case. In fact, many applications that require this type of QoS support do not have RSVP capabilities. So, in this recipe, we show how to configure the routers themselves to initiate requests on behalf of the hosts.

That recipe also contains information about the basic RSVP configurations used on the routers between Router1 and Router4 (which we have mysteriously decided to call Router2 and Router3).

The ip rsvp sender command tells the router to act as if it is periodically receiving RSVP PATH requests from the specified source device:

Router1(config)#ip rsvp sender 192.168.9.100 192.168.100.202 UDP 1300 1300 192.168.100.202 FastEthernet0/0 55 1

You use this command as a proxy for a real device that is unable to send real RSVP PATH requests. So it includes all of the information that appears in a PATH request packet.

The first several arguments of this command specify the IP flow that will be using this reservation. The first two arguments specify the source and destination IP addresses, respectively. Then we have stipulated that it will use the UDP protocol with source and destination ports both equal to 1300.

The next two arguments, 192.168.100.202 and FastEthernet0/0, specify the previous-hop IP address and interface, respectively. Because we put this command on the first hop router, they may seem redundant, but actually we could put this command anywhere in the network to simulate an upstream source device.

The last two arguments request an average bit rate of 55 kbps and a burst of 1 kbyte.

Then, on the other router, we have configured a corresponding command that simulates a device sending RSVP RESV messages back toward the source:

Router4(config)#ip rsvp reservation 192.168.9.100 192.168.100.202 UDP 1300 1300 192.168.9.100 Ethernet0/0 FF RATE 55 1

Many of the arguments of this command are identical to what we saw a moment ago for the sender command. We specified the same IP addresses and UDP port numbers to define the flow. And the last two arguments just duplicate the average bit rate and burst size from the previous discussion.

The differences are where the sender command specified the previous-hop IP address and interface, here we specify the next-hop IP address and interface. Then we have two new keywords, FF and RATE.

The FF keyword indicates that this is a Fixed Filter style reservation. There are three available styles of reservation. Fixed Filter means that this reservation is for a particular flow specification only. No other applications or sessions are permitted to use it. We could have instead specified either SE or WF.

SE indicates that the router will use a Shared Explicit filter for the reservation. This means that the receiving device is specifying a list of source devices and indicating that they may all share the same reservation.

And WF means that the reservation can be shared by a Wildcard Filter. This effectively means that any source can take part in this reservation.

Finally, the RATE keyword in the ip rsvp reservation command tells the network to use Guaranteed Bit Rate service type. The other option here is LOAD, which indicates a Controlled Load service type. The receiver makes this service type request, which is why it only appears in the ip rsvp reservation command, and not in the ip rsvp sender command.

There are several useful commands for looking at the RSVP reservations. You can look at the current status of any PATH and RESV messages passing through your network with the show ip rsvp sender and show ip rsvp reservation commands. These commands give the full details on every such RSVP exchange, whether it originates with a static command on the router, as in this recipe, or a dynamically generate request from a real host:

Router1#show ip rsvp sender
To              From            Pro DPort Sport Prev Hop        I/F      BPS
192.168.9.100   192.168.100.202 UDP 1300  1300  192.168.100.202 Fa0/0    55K
Router1#show ip rsvp reservation
To            From          Pro DPort Sport Next Hop      I/F      Fi Serv BPS
192.168.9.100 192.168.100.202 UDP 1300  1300  192.168.55.10 Se0/0.1  FF RATE 55K

Router1#

So if we go to another router in the path and enter these commands again, we see the same information:

Router2#show ip rsvp sender
To              From            Pro DPort Sport Prev Hop        I/F      BPS
192.168.9.100   192.168.100.202 UDP 1300  1300  192.168.55.9    Se0/0.1  55K
Router2#show ip rsvp reservation
To            From          Pro DPort Sport Next Hop      I/F      Fi Serv BPS
192.168.9.100 192.168.100.202 UDP 1300  1300  192.168.101.7 Fa0/0    FF RATE 55K

Router2#
Post in CCIE R&S | No Comments »

about CCIE Bootcamp.

February 7th, 2012   by Daniel

It truly is aimed to pick out the specialists inside the networking commerce for that famend firm providing opportunities with the specialized departments. With a function to get CCIE certification the candidates really need to transfer by two appropriate choice tests. First of all, the authored exam should be to be handed after which the candidates can sit for the Lab exam. The brief-listed candidates can exclusively have CCIE certification. In order to prepare for the CCIE exams, CCIE Bootcamp is fashioned.

CCIE Bootcamps provide basically probably the most handy strategy of passing out the checks of CCIE. There are actually many corporations reasonably institutes which supply CCIE Bootcamp education comparable to Cathay Faculty. Which includes a look at to grow to be qualified for your bootcamps the institutes often current a prerequisite. It helps to boost the prospect belonging to the applicants to maneuver the CCIE exams in a very higher way than most people. This prerequisite is referred to as CCNP position.

The connected fee for using the CCIE Stability test is large, so most candidates go for the preparation program to cross it in one sitting. Some unbiased firms and establishments deliver programs and workshop to individuals choosing CCIE Stability coaching. Even so, most candidates choose to make use of the instructor-led and on-line workshops, which Cisco furnish, like a element of Licensed Learning Companions application. The teaching selections are offered along with the educators are accepted by Cisco.

For the CCIE Security certification, you should sign-up for that composed examination with your area of specialization. Every one of the exams are done for the Cisco approved facility, which also accepts charge for the exam. The price of taking a CCIE written examination is from $80 to $325. The created test is supervised and done on a notebook computer. It's of 1 or two hrs paper containing quite a few selections, drag and drop doubts and fill within the blanks. Apart from white boards and markers for calculations, as being a candidate for CCIE Safety coaching examination, you aren't allowed to carry almost every other item to your test corridor.

CCIE Bootcamp is accompanied which includes a amount of practices to deliver the simplest preparation substance for the pupils. They principally provide some must-have books to prepare them for your composed CCIE get a glance at jointly with some web access for that Lab exam. Counting on these two classes the CCIE Bootcamps is divided into two sections. The divisions are course building and also Lab simulation. The class construction consists of two phases and they are fingers-on coaching and lectured-based mainly lessons. Within just the category composition the college students are offered considering the knowledge of Bit splitting, VLSM etc. But the lab simulation is critical aspect of CCIE Bootcamp. Right here the students are subjected to cope with a variety of real-life difficulties plus the troubleshooting skills are checked the right way. That is definitely the best phase of CCIE Bootcamps the spot the scholars are nicely-prepared for your Blueprintv4, MPLS and so on. These methodologies support college students to troubleshoot any real-life dilemmas and advance the ability to learn the proper remedies.

But there are couple of trustworthy institutes available for sale with the current market which delivers full CCIE Bootcamps. One among a great number of properly-renowned institutes is Cathay College which renders exceedingly really good providers in the event of bootcamps for CCIE. They provide bootcamp facilities to truly colossal variety of college pupils from many corners of the world like Australia, Norway, Uk, Sweden, USA and a great many a great deal more. In accordance together with the figures of this institute from 2005, they're sustaining document selection of proportion of passing fee in CCIE test. This file is alone a form of guarantee for them. There are many triggers to choose out Cathay School for CCIE Bootcamps. The report variety of passing rate of nearly 90% is easily the most beautiful functionality of it. Besides it, a single other exceptional characteristic often is the one-to-one lab coaching which benefit the college students to filter out each of the doubts about any draw back from your instructors.

The demanded detail regarding the bootcamp is available to your reliable supplier page which can be cathayschool.com. It's a fairly convenient site which will provide many different placing facilities like on-line Self-Study CCIE Lab Workbooks, one-on-one web based coaching, Teacher Led exercise etcetera. All the facilities and therefore the program durations together together with the money are effectively-described here this sort of which the shoppers may want to not ought to encounter any sort of problem relating to CCIE Bootcamps.

Post in CCIE Security | No Comments »

Manual RSVP Reservations

February 6th, 2012   by Daniel

In this example, we will assume that we have a host device, acting as the sender, with IP address 192.168.100.202 and a second host, acting as the receiver, with IP address 192.168.9.100. The first host is connected to FastEthernet0/0 Router1:

Router1#configure terminal
Enter configuration commands, one per line.  End with CNTL/Z.
Router1(config)#interface FastEthernet0/0
Router1(config-if)#ip address 192.168.100.21 255.255.255.0
Router1(config-if)#ip rsvp bandwidth 128 56
Router1(config-if)#exit
Router1(config)#interface Serial0/0
Router1(config-if)#no ip address
Router1(config-if)#encapsulation frame-relay
Router1(config-if)#fair-queue 64 256 37
Router1(config-if)#ip rsvp bandwidth
Router1(config-if)#exit
Router1(config)#interface Serial0/0.1 point-to-point
Router1(config-subif)#ip address 192.168.55.9 255.255.255.252
Router1(config-subif)#frame-relay interface-dlci 904
Router1(config-fr-dlci)#ip rsvp bandwidth 128 56
Router1(config-subif)#exit
Router1(config)#ip rsvp sender 192.168.9.100 192.168.100.202 UDP 1300 1300 192.168.100.202 FastEthernet0/0 55 1
Router1(config)#end
Router1#

The second host is connected to the Ethernet0/0 interface on Router4, which is several hops away:

Router4# configure terminal
Router4(config)#interface Ethernet0/0
Router4(config-if)#ip address 192.168.9.3 255.255.255.0
Router4(config-if)#ip rsvp bandwidth 128 56
Router4(config-if)#exit
Router4(config)#interface Serial0/0
Router4(config-if)#no ip address
Router4(config-if)#encapsulation frame-relay
Router4(config-if)#fair-queue 64 256 37
Router4(config-if)#ip rsvp bandwidth
Router4(config-if)#exit
Router4(config)#interface Serial0/0.1 point-to-point
Router4(config-subif)#ip address 192.168.56.5 255.255.255.252
Router4(config-subif)#frame-relay interface-dlci 107
Router4(config-fr-dlci)#ip rsvp bandwidth 128 56
Router4(config-subif)#exit
Router4(config)#ip rsvp reservation 192.168.9.100 192.168.100.202 UDP 1300 1300 192.168.9.100 Ethernet0/0 FF RATE 55 1
Router4(config)#end
Router4#

It is worthwhile to review how RSVP works before looking at the mechanics of this recipe. A host that wants to send a data stream to a particular destination address or multicast group first makes an RSVP request to its first-hop router. This request asks for a particular set of QoS parameters, such as application bandwidth requirements, and specifies the destination IP address. Each router decides whether it can meet the requirement, accepting or rejecting the reservation. They then make the same request of the next hop router along the path to the destination. Once all of the routers between the source and destination have reserved the appropriate resources, the original host can begin transmitting application data, using the reserved resources along the entire data path.

The method is identical for unicast and multicast reservation requests, with each router relaying the request to a downstream peer until all of the destinations have been reached. Note that RSVP is inherently unidirectional. That is, it requests resources for sending data from a particular source to a particular destination or multicast group. If you want to reserve network resources to support a two-way unicast application, both the sender and the receiver must separately initiate requests.

RESV and PATH messages

There are two general message types in RSVP, PATH, and RESV. The initial request begins with a PATH message. The PATH message describes the specific flow that will use this reservation. So it includes the source and destination IP addresses, as well as the IP Protocol, such as TCP or UDP, and any port numbers. The PATH message also includes the requested average bit rate and burst size.

The PATH message is received by an upstream router, or perhaps the ultimate destination. If it is received by an intermediate router, this router must analyze the request and decide whether it can honor it. Ultimately, if the request is accepted, the router will create a new PATH message, requesting the same resource reservation from the next upstream router, but specifying itself as the source.

PATH messages always flow from the requester toward the destination.

RESV messages flow the opposite direction. The RESV CONFIRM messages describe the actual detailed bit rate and delay characteristics required to fulfill the PATH request. If an upstream router doesn't have the necessary resource to fulfill the request, it responds with an RESV ERROR message.

In Cisco router configuration, you can configure static PATH requests by using the ip rsvp sender and sender-host commands. And you can make static reservations, which will be described to upstream routers in RESV messages, using the ip rsvp reserveration and reservation-host commands. We will describe all of these commands below.

Two service types

There are two distinct types of service that a host can specify in an RSVP request. The first is called Controlled Load Service, which is specified in RFC 2211, and the second, called either Guaranteed Quality of Service or, more accurately, Guaranteed Bit Rate Service, is specified in RFC 2212.

Controlled Load Service, in a nutshell, means that the network behaves as if each segment were completely unloaded and therefore uncongested, but with bandwidth limited to the requested amount. Cisco routers implement this type of service by isolating the different flows and employing queuing mechanisms that mimic this type of response.

Guaranteed Bit Rate Service is somewhat more complicated. This service means that the network will mathematically guarantee the worst-case end-to-end queuing delay. There are two things to note about this description, however. First, it only guarantees the worst-case latency, not the average latency. The second is that, despite this, it is possible to make an estimate of the jitter, as this is governed by the worst-case latency. As long as the worst-case latency is small, then the jitter can be effectively minimized by employing small amounts of buffering on the end devices.

Controlled Load Service is well suited to many TCP applications, which tend to behave well until they encounter congestion and dropped packets. Conversely, Guaranteed Bit Rate Service tends to be a better choice for real-time voice and video applications.

The examples

Everything we have described so far implies that the source and destination host devices or applications are making the RSVP requests. However, this is not necessarily the case. In fact, many applications that require this type of QoS support do not have RSVP capabilities. So, in this recipe, we show how to configure the routers themselves to initiate requests on behalf of the hosts.

That recipe also contains information about the basic RSVP configurations used on the routers between Router1 and Router4 (which we have mysteriously decided to call Router2 and Router3).

The ip rsvp sender command tells the router to act as if it is periodically receiving RSVP PATH requests from the specified source device:

Router1(config)#ip rsvp sender 192.168.9.100 192.168.100.202 UDP 1300 1300 192.168.100.202 FastEthernet0/0 55 1

You use this command as a proxy for a real device that is unable to send real RSVP PATH requests. So it includes all of the information that appears in a PATH request packet.

The first several arguments of this command specify the IP flow that will be using this reservation. The first two arguments specify the source and destination IP addresses, respectively. Then we have stipulated that it will use the UDP protocol with source and destination ports both equal to 1300.

The next two arguments, 192.168.100.202 and FastEthernet0/0, specify the previous-hop IP address and interface, respectively. Because we put this command on the first hop router, they may seem redundant, but actually we could put this command anywhere in the network to simulate an upstream source device.

The last two arguments request an average bit rate of 55 kbps and a burst of 1 kbyte.

Then, on the other router, we have configured a corresponding command that simulates a device sending RSVP RESV messages back toward the source:

Router4(config)#ip rsvp reservation 192.168.9.100 192.168.100.202 UDP 1300 1300 192.168.9.100 Ethernet0/0 FF RATE 55 1

Many of the arguments of this command are identical to what we saw a moment ago for the sender command. We specified the same IP addresses and UDP port numbers to define the flow. And the last two arguments just duplicate the average bit rate and burst size from the previous discussion.

The differences are where the sender command specified the previous-hop IP address and interface, here we specify the next-hop IP address and interface. Then we have two new keywords, FF and RATE.

The FF keyword indicates that this is a Fixed Filter style reservation. There are three available styles of reservation. Fixed Filter means that this reservation is for a particular flow specification only. No other applications or sessions are permitted to use it. We could have instead specified either SE or WF.

SE indicates that the router will use a Shared Explicit filter for the reservation. This means that the receiving device is specifying a list of source devices and indicating that they may all share the same reservation.

And WF means that the reservation can be shared by a Wildcard Filter. This effectively means that any source can take part in this reservation.

Finally, the RATE keyword in the ip rsvp reservation command tells the network to use Guaranteed Bit Rate service type. The other option here is LOAD, which indicates a Controlled Load service type. The receiver makes this service type request, which is why it only appears in the ip rsvp reservation command, and not in the ip rsvp sender command.

There are several useful commands for looking at the RSVP reservations. You can look at the current status of any PATH and RESV messages passing through your network with the show ip rsvp sender and show ip rsvp reservation commands. These commands give the full details on every such RSVP exchange, whether it originates with a static command on the router, as in this recipe, or a dynamically generate request from a real host:

Router1#show ip rsvp sender
To              From            Pro DPort Sport Prev Hop        I/F      BPS
192.168.9.100   192.168.100.202 UDP 1300  1300  192.168.100.202 Fa0/0    55K
Router1#show ip rsvp reservation
To            From          Pro DPort Sport Next Hop      I/F      Fi Serv BPS
192.168.9.100 192.168.100.202 UDP 1300  1300  192.168.55.10 Se0/0.1  FF RATE 55K

Router1#

So if we go to another router in the path and enter these commands again, we see the same information:

Router2#show ip rsvp sender
To              From            Pro DPort Sport Prev Hop        I/F      BPS
192.168.9.100   192.168.100.202 UDP 1300  1300  192.168.55.9    Se0/0.1  55K
Router2#show ip rsvp reservation
To            From          Pro DPort Sport Next Hop      I/F      Fi Serv BPS
192.168.9.100 192.168.100.202 UDP 1300  1300  192.168.101.7 Fa0/0    FF RATE 55K

Router2#
Post in CCIE Labs | No Comments »

CCIESecurityTrainingschooling

February 4th, 2012   by Daniel

There just isn't a have got to have an additional experienced schooling or class certificates to qualify.

The CCIESecurityTrainingtraining consists of a prepared examination to qualify then the lab test. You are advised to get for the minimum 3-5 ages of employment expertise earlier than making an attempt this certification.

The examination for your CCIE Stability is of two-hour duration with multiple choices. This is made of hundred thoughts, which can cover topics equal to software protocols, operating systems, safety technologies, security protocols, and Cisco security programs. The examination materials are supplied within the spot and you also are not authorized to usher in external reference materials.

Network engineers having a CCIE certificates are thought of as since the expert while in the community engineering self-discipline in addition to the masters of CISCO merchandise. The CCIE has introduced revolution inside of the neighborhood market place regarding technically hard assignments and possibilities with all the necessary instruments and methodologies. You can find a method which updates and reorganizes the instruments to provide level of quality service. You can find numerous modes of CCIE Coaching like published examination preparation and performance dependent lab. This aids to reinforce the effectivity and regular for the community. CISCO has launched this certification policy in 1993 by having a see to tell apart the very best professionals from your relaxation.

In order to be licensed, very first published examination should be passed immediately after which must cross the lab test. CISCO in any way moments tries to apply fully varied CCIE Workout methods for increased efficiency. There are a number of actions for your CCIE certification. The first stage for certification is to try to move a two hours lasting computer system based generally MCQ oriented prepared exam. For this exam vital payments must be completed via internet based. This examination is related with examination vouchers and promotional codes. The authenticity of the voucher providing firm must be nicely regarded with the candidates. The promotional code should really be accessed effectively and in the event of fraudulent vouchers alongside promotional codes shouldn't satisfactory and CISCO will not repay the value. The candidates must wait around five days for the written examination following fee and they can't sit for that same exact exam for the subsequent 100 eighty days in the event of recertification.

That has a watch to obtain certified and eligible for the CCIE Schooling some components are to become remembered efficiently. As a result of passing the developed examination the candidates use a nearly all of 18 months time for wanting the lab test. If the time period exceeds then the authenticity from the authored test could be invalid. For that first of all timer utilized to possess CCIE certification the created examination is available in the kind of Beta examination with discount rates offered. In the Beta time period the candidates can sit only the moment for the examination. The results will arrive within six to eight weeks immediately after the examination is over.

The next phase for that CCIE certification often is the Lab test. The shortlisted candidates of your written examination can solely use for your fingers-on lab test. Even though there are many penned examination centers of CISCO although Lab exam services are confined. It can be an eight hour fingers-on useful based largely examination wherein the power of troubleshooting and configuring local community mostly primarily based problems and software are checked. For your scheduling of Lab examination the shortlisted candidates of your before prepared examination have got to present the identification amount as well as passing ranking and then the date of passing.

The cost for Lab examination must be cleared before than 90 days of this scheduled test. With out the charge the reservation can be cancelled. Right after passing the Lab test blended along with the published examination the candidates can implement for your CCIE certification. By considering

Post in CCIE R&S | No Comments »

Environment the DSCP or TOS Discipline

February 3rd, 2012   by Daniel

The answer to this concern depends on the sort of potential customers distinctions you're looking for to make, also the model of IOS you could be managing in your routers.

There will have to be something that defines the various sorts of page views you wish to prioritize. Generally, the easier the distinctions are for making, the higher. It is because all of the tests just take router sources and introduce processing delays. The commonest rules for distinguishing in between site traffic types use the packet's input interface and straightforward IP header facts this sort of as TCP port figures. The subsequent examples demonstrate techniques to set an IP Precedence worth of instant (2) for all FTP regulate potential customers that arrives by using the serial0/0 interface, and an IP Precedence of priority (1) for all FTP info website traffic. This distinction is possible for the reason that FTP manage targeted traffic usages TCP port 21, and FTP information usages port twenty.

The new methodology for configuring this usages course maps. Cisco initially introduced this attribute in IOS Model twelve.0(5)T. This process initial defines a class-map that specifies how the router will determine this kind of visitors. It then defines a policy-map that really makes the alterations on the packet's TOS area:

Router#configure terminal
Enter configuration commands, one per line.  End with CNTL/Z.
Router(config)#access-list 101 permit any eq ftp any
Router(config)#access-list 101 permit any any eq ftp
Router(config)#access-list 102 permit any eq ftp-data any
Router(config)#access-list 102 permit any any eq ftp-data
Router(config)#class-map match-all ser00-ftpcontrol
Router(config-cmap)#description branch ftp control traffic
Router(config-cmap)#match input-interface serial0/0
Router(config-cmap)#match access-group 101
Router(config-cmap)#exit
Router(config)#class-map match-all ser00-ftpdata
Router(config-cmap)#description branch ftp data traffic
Router(config-cmap)#match input-interface serial0/0
Router(config-cmap)#match access-group 102
Router(config-cmap)#exit
Router(config)#policy-map serialftppolicy
Router(config-pmap)#description branch ftp traffic policy
Router(config-pmap)#class ser00-ftpcontrol
Router(config-pmap-c)#set ip precedence immediate
Router(config-pmap-c)#exit
Router(config-pmap)#class ser00-ftpdata
Router(config-pmap-c)#set ip precedence priority
Router(config-pmap-c)#exit
Router(config-pmap)#exit
Router(config)#interface serial0/0
Router(config-if)#ip route-cache policy
Router(config-if)#service-policy input serialftppolicy
Router(config-if)#exit
Router(config)#end
Router#

For earlier IOS variations, exactly where class-maps ended up not on hand, you've make use of policy-based routing to alter the TOS discipline in the packet. Applying this coverage on the interface tells the router to work with this policy to test all incoming packets on this interface and rewrite the ones that match the route map:Router#configure terminal

Enter configuration commands, one per line.  End with CNTL/Z.
Router(config)#access-list 101 permit any eq ftp any
Router(config)#access-list 101 permit any any eq ftp
Router(config)#access-list 102 permit any eq ftp-data any
Router(config)#access-list 102 permit any any eq ftp-data
Router(config)#route-map serialftp-rtmap permit 10
Router(config-route-map)#match ip address 101
Router(config-route-map)#set ip precedence immediate
Router(config-route-map)#exit
Router(config)#route-map serialftp-rtmap permit 20
Router(config-route-map)#match ip address 102
Router(config-route-map)#set ip precedence priority
Router(config-route-map)#exit
Router(config)#interface serial0/0
Router(config-if)#ip policy route-map serialftp-rtmap
Router(config-if)#ip route-cache policy
Router(config-if)#exit
Router(config)#end
Router#

Prior to you are able to tag a packet for exceptional remedy, you will have to have a particularly obvious notion of what different types of site traffic desire exclusive therapy, and also precisely what sort of special remedy they may really need. From the case in point, we have made a decision to give a wonderful priority to FTP site visitors received on the particular serial interface. We demonstrate how one can do this employing both the old and new configuration methods.
This will appear to get a rather synthetic illustration. As a result of all, why would you treatment about tagging inbound website traffic you have already acquired from a low-speed interface? Essentially, amongst the most critical principles for implementing QoS in a network is the fact you ought to frequently tag the packet as early as feasible, ideally at the edges from the network. Then, since it passes throughout the network, just about every router only must look into the tag, and isn't going to will want to do any further classification. In this case, we might make sure that the FTP site traffic returning around the other gouvernement is tagged because of the initially router that receives it. And so the outbound page views has already been tagged, and it is a waste of router resources to reclassify the outbound packets.

A great number of organizations literally get this concept of marking on the edges a single stage more, and remark just about every acquired packet. This can help to guarantee that end users aren't requesting special QoS privileges they aren't allowed to get. At the same time, you need to be watchful of this given that it can typically disrupt legitimate markings. For instance, a real-time software would most likely use RSVP to order bandwidth in the network. It is actually important the packets for this application possess the ideal Expedited Forwarding (EF) DSCP marking or perhaps the network may not manage them competently. Although, you also really don't like to allow other non-real-time applications from this similar source have the same EF concern stage. So, should you be going to configure your routers to remark all incoming packets at the edges, make sure you know what incoming markings are respectable.

In that circumstance, the routers are managing DLSw to bridge SNA potential customers by an IP network. So the routers by themselves definitely set up the IP packets. This generates an additional challenge seeing that there is certainly no incoming interface. To make sure that recipe takes advantage of regional policy-based routing. The very fact that the router makes the packets also presents it an essential benefit considering the fact that it does not have to take into consideration any DLSw packets that may just transpire to go through.

The benefits on the newer class-map way are not apparent in this particular instance, but among the first great features seems in order for you to work with the more fashionable DSCP tagging scheme. As the older policy-based routing method will not immediately support DSCP, you've got to pretend it by setting each the IP Precedence and also TOS individually as follows.

Router(config)#route-map serialftp-rtmap permit 10
Router(config-route-map)#match ip address 115
Router(config-route-map)#set ip precedence immediate
Router(config-route-map)#set ip tos max-throughput

In this case, the packet will wind up with an IP Precedence value of immediate, or 2 (010 in binary), and TOS of max-throughput, or 4 (0100 in binary).

Doing the same thing with the class-map method is much more direct:

Router(config)#policy-map serialftppolicy
Router(config-pmap)#class serialftpclass
Router(config-pmap-c)#set ip dscp af21

Class-maps may even be advantageous later on in such a chapter after we discuss class-based weighted reasonable queuing and class-based targeted traffic shaping.
It is crucial to notice that all through this whole example, we have now only set a particular price into your packet's TOS or DSCP discipline. This, by by itself, would not have an affect on how the packet is forwarded by means of the network. To carry out that, you must be certain that as each router inside network forwards these marked packets, the interface queues will react appropriately to this data.

Finally, we should always notice that as this recipe demonstrates two advantageous tactics of marking packets, implementing Dedicated Accessibility Fee (Motor vehicle) benefits. Car tends to become a lot more efficient on greater speed interfaces.

Post in CCIE R&S | No Comments »

Fast Switching and CEF

February 2nd, 2012   by Daniel

As we discuss in Appendix B, one of the most important things you can do to improve router performance, and consequently network performance, is to ensure that you are using the best packet switching algorithm. All Cisco routers support Fast Switching, and it is enabled by default. However, some types of configurations require that it be disabled. The following example shows how to turn Fast Switching back on if it has been disabled:

Router#configure terminal
Enter configuration commands, one per line.  End with CNTL/Z.
Router(config)#interface FastEthernet0/0
Router(config-if)#ip route-cache
Router(config-if)#exit
Router(config)#end
Router#

If you are using policies, including policies for Class-based QoS, you also need to configure Fast Switching to handle them, using the ip route-cache policy command:

Router#configure terminal
Enter configuration commands, one per line.  End with CNTL/Z.
Router(config)#interface FastEthernet0/0
Router(config-if)#ip route-cache policy
Router(config-if)#exit
Router(config)#end
Router#

CEF, on the other hand, is not enabled by default. Unlike Fast Switching, which is enabled separately for each interface, you have to enable CEF globally for the entire router, as well as on each interface:

Router#configure terminal
Enter configuration commands, one per line.  End with CNTL/Z.
Router(config)#ip cef
Router(config)#interface FastEthernet0/0
Router(config-if)#ip route-cache cef
Router(config-if)#exit
Router(config)#end
Router#

The ip route-cache command used to enable Fast Switching has a couple of useful options. The second example demonstrates one of these options, the policy keyword, which allows Fast Switching of policy-based routing:

Router(config-if)#ip route-cache policy

Another useful option is the same-interface keyword, which instructs the router to allow Fast Switching of packets that come in and go back out through the same physical interface:

Router(config)#interface Serial0/0
Router(config-if)#ip route-cache same-interface

You should use this option when the router frequently needs to switch packets between different networks that all connect to the same port. This could be the case for Frame Relay networks, as well as for LANs that use subinterfaces or secondary IP addresses.

Cisco supplies three useful commands to look at CEF performance. The first is show cef interface:

Router#show cef interface FastEthernet0/0
FastEthernet0/1 is up (if_number 4)
  Corresponding hwidb fast_if_number 4
  Corresponding hwidb firstsw->if_number 4
  Internet address is 172.22.1.3/24
  ICMP redirects are always sent
  Per packet load-sharing is disabled
  IP unicast RPF check is disabled
  Inbound access list is 120
  Outbound access list is not set
  IP policy routing is disabled
  Hardware idb is FastEthernet0/1
  Fast switching type 1, interface type 18
  IP CEF switching enabled
  IP CEF Feature Fast switching turbo vector
  Input fast flags 0x0, Output fast flags 0x0
  ifindex 4(4)
  Slot 0 Slot unit 1 VC -1
  Transmit limit accumulator 0x0 (0x0)
  IP MTU 1500
Router#

The output of this command shows that CEF is enabled on the interface FastEthernet0/0, as well as information about inbound and outbound ACL's and policies. In this example, you can see that the interface has an access-group configured to use access-list number 120 to filter inbound traffic.

You can use the show cef drop and show cef not-cef-switched commands to see more detailed CEF forwarding statistics:

Router#show cef drop
CEF Drop Statistics
Slot  Encap_fail  Unresolved Unsupported    No_route      No_adj  ChkSum_Err
RP            71           0           0         105           0           0
Router#show cef not-cef-switched
CEF Packets passed on to next switching layer
Slot  No_adj No_encap Unsupp'ted Redirect  Receive  Options   Access     Frag
RP         0       0           0        0      572        0        0        0

These commands show you details of CEF's operation on the router. The first command shows how many packets CEF has had to drop, and the reasons for the drops. The Slot column in the output of both commands refers to the VIP slot where the packets were received. In this case, the router didn't have any VIP cards because it was a Cisco 2600. So all packets are received by the Route Processor, which is indicated by the RP in the leftmost column.

The Encap_fail column in the show cef drop output shows the number of packets that CEF has dropped because they were incomplete and there was no adjacency route in the CEF table. Unresolved indicates the number of packets dropped because CEF could not resolve the destination address prefix. If there had been any packets that could not be switched by CEF because of unsupported features, they would appear in the Unsupported column. The No_route column shows the number of packets dropped because CEF didn't have a route to the destination. Similarly, No_adj shows the number of packets for which CEF did not have an entry in its adjacency table, so it had to send an ARP query. And, finally, ChkSum_Err shows the number of times that CEF had to drop packets because they were corrupted.

The show cef not-cef-switched command has similar output. No_adj is the same here as it was in the show cef drop command, while Unsupp'ted is the same as the Unsupported column. The No_encap column counts the number of packets that could not be switched because they were encapsulated in another protocol. Redirect means that CEF has had to send these packets to another algorithm, usually process switching, to handle. And Receive lists the number of packets that were received from another internal switching algorithm. The remaining columns are rarely of interest in practice.

You can display the CEF version of the routing table with the show ip cef command:

Router#show ip cef
Prefix              Next Hop             Interface
0.0.0.0/0           172.25.1.1           FastEthernet0/0.1
0.0.0.0/32          receive
172.16.2.0/24       attached             FastEthernet0/1
                    attached             FastEthernet1/1
172.22.1.0/24       attached             FastEthernet0/1
172.22.1.0/32       receive
172.22.1.3/32       receive
172.22.1.4/32       172.22.1.4           FastEthernet0/1
<many lines deleted>
Router#

Notice in this output that there are actually two equal-cost routes to 172.16.2.0/24. CEF supports load balancing between these two paths.

You can expand the detail on these entries with the show ip cef detail command:

Router#show ip cef detail
IP CEF with switching (Table Version 31), flags=0x0
  31 routes, 0 reresolve, 0 unresolved (0 old, 0 new), peak 1
  31 leaves, 21 nodes, 25560 bytes, 62 inserts, 31 invalidations
  0 load sharing elements, 0 bytes, 0 references
  universal per-destination load sharing algorithm, id 0697166A
  3(1) CEF resets, 0 revisions of existing leaves
  Resolution Timer: Exponential (currently 1s, peak 1s)
  0 in-place/0 aborted modifications
  refcounts:  5672 leaf, 5632 node

Adjacency Table has 5 adjacencies
0.0.0.0/0, version 27, cached adjacency 172.25.1.1
0 packets, 0 bytes
  via 172.25.1.1, FastEthernet0/0.1, 0 dependencies
    next hop 172.25.1.1, FastEthernet0/0.1
    valid cached adjacency
0.0.0.0/32, version 0, receive
172.16.2.0/24, version 21, attached, connected
0 packets, 0 bytes
  via FastEthernet0/0.2, 0 dependencies
    valid glean adjacency
172.16.2.0/32, version 10, receive
172.16.2.1/32, version 9, receive
172.16.2.255/32, version 11, receive
172.22.1.0/24, version 22, attached, connected
0 packets, 0 bytes
  via FastEthernet0/1, 0 dependencies
    valid glean adjacency
172.22.1.0/32, version 16, receive
<many lines deleted>
Router#
Post in CCIE Labs | No Comments »

CCIE Bootcamps, CCIE Lab Exam

January 30th, 2012   by Daniel

The answer to this concern depends on the sort of potential customers distinctions you're looking for to make, also the model of IOS you could be managing in your routers. CCIE Bootcamps

There will have to be something that defines the various sorts of page views you wish to prioritize. Generally, the easier the distinctions are for making, the higher. It is because all of the tests just take router sources and introduce processing delays. The commonest rules for distinguishing in between site traffic types use the packet's input interface and straightforward IP header facts this sort of as TCP port figures. The subsequent examples demonstrate techniques to set an IP Precedence worth of instant (2) for all FTP regulate potential customers that arrives by using the serial0/0 interface, and an IP Precedence of priority (1) for all FTP info website traffic. This distinction is possible for the reason that FTP manage targeted traffic usages TCP port 21, and FTP information usages port twenty.

The new methodology for configuring this usages course maps. Cisco initially introduced this attribute in IOS Model twelve.0(5)T. This process initial defines a class-map that specifies how the router will determine this kind of visitors. It then defines a policy-map that really makes the alterations on the packet's TOS area:

Router#configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
Router(config)#access-list 101 permit any eq ftp any
Router(config)#access-list 101 permit any any eq ftp
Router(config)#access-list 102 permit any eq ftp-data any
Router(config)#access-list 102 permit any any eq ftp-data
Router(config)#class-map match-all ser00-ftpcontrol
Router(config-cmap)#description branch ftp control traffic
Router(config-cmap)#match input-interface serial0/0
Router(config-cmap)#match access-group 101
Router(config-cmap)#exit
Router(config)#class-map match-all ser00-ftpdata
Router(config-cmap)#description branch ftp data traffic
Router(config-cmap)#match input-interface serial0/0
Router(config-cmap)#match access-group 102
Router(config-cmap)#exit
Router(config)#policy-map serialftppolicy
Router(config-pmap)#description branch ftp traffic policy
Router(config-pmap)#class ser00-ftpcontrol
Router(config-pmap-c)#set ip precedence immediate
Router(config-pmap-c)#exit
Router(config-pmap)#class ser00-ftpdata
Router(config-pmap-c)#set ip precedence priority
Router(config-pmap-c)#exit
Router(config-pmap)#exit
Router(config)#interface serial0/0
Router(config-if)#ip route-cache policy
Router(config-if)#service-policy input serialftppolicy
Router(config-if)#exit
Router(config)#end
Router#

For earlier IOS variations, exactly where class-maps ended up not on hand, you've make use of policy-based routing to alter the TOS discipline in the packet. Applying this coverage on the interface tells the router to work with this policy to test all incoming packets on this interface and rewrite the ones that match the route map:Router#configure terminal

Enter configuration commands, one per line. End with CNTL/Z.
Router(config)#access-list 101 permit any eq ftp any
Router(config)#access-list 101 permit any any eq ftp
Router(config)#access-list 102 permit any eq ftp-data any
Router(config)#access-list 102 permit any any eq ftp-data
Router(config)#route-map serialftp-rtmap permit 10
Router(config-route-map)#match ip address 101
Router(config-route-map)#set ip precedence immediate
Router(config-route-map)#exit
Router(config)#route-map serialftp-rtmap permit 20
Router(config-route-map)#match ip address 102
Router(config-route-map)#set ip precedence priority
Router(config-route-map)#exit
Router(config)#interface serial0/0
Router(config-if)#ip policy route-map serialftp-rtmap
Router(config-if)#ip route-cache policy
Router(config-if)#exit
Router(config)#end
Router#

Prior to you are able to tag a packet for exceptional remedy, you will have to have a particularly obvious notion of what different types of site traffic desire exclusive therapy, and also precisely what sort of special remedy they may really need. From the case in point, we have made a decision to give a wonderful priority to FTP site visitors received on the particular serial interface. We demonstrate how one can do this employing both the old and new configuration methods.
This will appear to get a rather synthetic illustration. As a result of all, why would you treatment about tagging inbound website traffic you have already acquired from a low-speed interface? Essentially, amongst the most critical principles for implementing QoS in a network is the fact you ought to frequently tag the packet as early as feasible, ideally at the edges from the network. Then, since it passes throughout the network, just about every router only must look into the tag, and isn't going to will want to do any further classification. In this case, we might make sure that the FTP site traffic returning around the other gouvernement is tagged because of the initially router that receives it. And so the outbound page views has already been tagged, and it is a waste of router resources to reclassify the outbound packets.

A great number of organizations literally get this concept of marking on the edges a single stage more, and remark just about every acquired packet. This can help to guarantee that end users aren't requesting special QoS privileges they aren't allowed to get. At the same time, you need to be watchful of this given that it can typically disrupt legitimate markings. For instance, a real-time software would most likely use RSVP to order bandwidth in the network. It is actually important the packets for this application possess the ideal Expedited Forwarding (EF) DSCP marking or perhaps the network may not manage them competently. Although, you also really don't like to allow other non-real-time applications from this similar source have the same EF concern stage. So, should you be going to configure your routers to remark all incoming packets at the edges, make sure you know what incoming markings are respectable.

In that circumstance, the routers are managing DLSw to bridge SNA potential customers by an IP network. So the routers by themselves definitely set up the IP packets. This generates an additional challenge seeing that there is certainly no incoming interface. To make sure that recipe takes advantage of regional policy-based routing. The very fact that the router makes the packets also presents it an essential benefit considering the fact that it does not have to take into consideration any DLSw packets that may just transpire to go through.

The benefits on the newer class-map way are not apparent in this particular instance, but among the first great features seems in order for you to work with the more fashionable DSCP tagging scheme. As the older policy-based routing method will not immediately support DSCP, you've got to pretend it by setting each the IP Precedence and also TOS individually as follows.

Router(config)#route-map serialftp-rtmap permit 10
Router(config-route-map)#match ip address 115
Router(config-route-map)#set ip precedence immediate
Router(config-route-map)#set ip tos max-throughput

In this case, the packet will wind up with an IP Precedence value of immediate, or 2 (010 in binary), and TOS of max-throughput, or 4 (0100 in binary).

Doing the same thing with the class-map method is much more direct:

Router(config)#policy-map serialftppolicy
Router(config-pmap)#class serialftpclass
Router(config-pmap-c)#set ip dscp af21

Class-maps may even be advantageous later on in such a chapter after we discuss class-based weighted reasonable queuing and class-based targeted traffic shaping.
It is crucial to notice that all through this whole example, we have now only set a particular price into your packet's TOS or DSCP discipline. This, by by itself, would not have an affect on how the packet is forwarded by means of the network. To carry out that, you must be certain that as each router inside network forwards these marked packets, the interface queues will react appropriately to this data.

Finally, we should always notice that as this recipe demonstrates two advantageous tactics of marking packets, implementing Dedicated Accessibility Fee (Motor vehicle) benefits. Car tends to become a lot more efficient on greater speed interfaces.

Post in CCIE Labs | No Comments »

CCIE Voice Training, Environment the DSCP or TOS Discipline

January 13th, 2012   by Daniel

The answer to this concern depends on the sort of potential customers distinctions you're looking for to make, also the model of IOS you could be managing in your routers. CCIE Voice Training

There will have to be something that defines the various sorts of page views you wish to prioritize. Generally, the easier the distinctions are for making, the higher. It is because all of the tests just take router sources and introduce processing delays. The commonest rules for distinguishing in between site traffic types use the packet's input interface and straightforward IP header facts this sort of as TCP port figures. The subsequent examples demonstrate techniques to set an IP Precedence worth of instant (2) for all FTP regulate potential customers that arrives by using the serial0/0 interface, and an IP Precedence of priority (1) for all FTP info website traffic. This distinction is possible for the reason that FTP manage targeted traffic usages TCP port 21, and FTP information usages port twenty.

The new methodology for configuring this usages course maps. Cisco initially introduced this attribute in IOS Model twelve.0(5)T. This process initial defines a class-map that specifies how the router will determine this kind of visitors. It then defines a policy-map that really makes the alterations on the packet's TOS area:

Router#configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
Router(config)#access-list 101 permit any eq ftp any
Router(config)#access-list 101 permit any any eq ftp
Router(config)#access-list 102 permit any eq ftp-data any
Router(config)#access-list 102 permit any any eq ftp-data
Router(config)#class-map match-all ser00-ftpcontrol
Router(config-cmap)#description branch ftp control traffic
Router(config-cmap)#match input-interface serial0/0
Router(config-cmap)#match access-group 101
Router(config-cmap)#exit
Router(config)#class-map match-all ser00-ftpdata
Router(config-cmap)#description branch ftp data traffic
Router(config-cmap)#match input-interface serial0/0
Router(config-cmap)#match access-group 102
Router(config-cmap)#exit
Router(config)#policy-map serialftppolicy
Router(config-pmap)#description branch ftp traffic policy
Router(config-pmap)#class ser00-ftpcontrol
Router(config-pmap-c)#set ip precedence immediate
Router(config-pmap-c)#exit
Router(config-pmap)#class ser00-ftpdata
Router(config-pmap-c)#set ip precedence priority
Router(config-pmap-c)#exit
Router(config-pmap)#exit
Router(config)#interface serial0/0
Router(config-if)#ip route-cache policy
Router(config-if)#service-policy input serialftppolicy
Router(config-if)#exit
Router(config)#end
Router#

For earlier IOS variations, exactly where class-maps ended up not on hand, you've make use of policy-based routing to alter the TOS discipline in the packet. Applying this coverage on the interface tells the router to work with this policy to test all incoming packets on this interface and rewrite the ones that match the route map:Router#configure terminal

Enter configuration commands, one per line. End with CNTL/Z.
Router(config)#access-list 101 permit any eq ftp any
Router(config)#access-list 101 permit any any eq ftp
Router(config)#access-list 102 permit any eq ftp-data any
Router(config)#access-list 102 permit any any eq ftp-data
Router(config)#route-map serialftp-rtmap permit 10
Router(config-route-map)#match ip address 101
Router(config-route-map)#set ip precedence immediate
Router(config-route-map)#exit
Router(config)#route-map serialftp-rtmap permit 20
Router(config-route-map)#match ip address 102
Router(config-route-map)#set ip precedence priority
Router(config-route-map)#exit
Router(config)#interface serial0/0
Router(config-if)#ip policy route-map serialftp-rtmap
Router(config-if)#ip route-cache policy
Router(config-if)#exit
Router(config)#end
Router#

Prior to you are able to tag a packet for exceptional remedy, you will have to have a particularly obvious notion of what different types of site traffic desire exclusive therapy, and also precisely what sort of special remedy they may really need. From the case in point, we have made a decision to give a wonderful priority to FTP site visitors received on the particular serial interface. We demonstrate how one can do this employing both the old and new configuration methods.
This will appear to get a rather synthetic illustration. As a result of all, why would you treatment about tagging inbound website traffic you have already acquired from a low-speed interface? Essentially, amongst the most critical principles for implementing QoS in a network is the fact you ought to frequently tag the packet as early as feasible, ideally at the edges from the network. Then, since it passes throughout the network, just about every router only must look into the tag, and isn't going to will want to do any further classification. In this case, we might make sure that the FTP site traffic returning around the other gouvernement is tagged because of the initially router that receives it. And so the outbound page views has already been tagged, and it is a waste of router resources to reclassify the outbound packets.

A great number of organizations literally get this concept of marking on the edges a single stage more, and remark just about every acquired packet. This can help to guarantee that end users aren't requesting special QoS privileges they aren't allowed to get. At the same time, you need to be watchful of this given that it can typically disrupt legitimate markings. For instance, a real-time software would most likely use RSVP to order bandwidth in the network. It is actually important the packets for this application possess the ideal Expedited Forwarding (EF) DSCP marking or perhaps the network may not manage them competently. Although, you also really don't like to allow other non-real-time applications from this similar source have the same EF concern stage. So, should you be going to configure your routers to remark all incoming packets at the edges, make sure you know what incoming markings are respectable.

In that circumstance, the routers are managing DLSw to bridge SNA potential customers by an IP network. So the routers by themselves definitely set up the IP packets. This generates an additional challenge seeing that there is certainly no incoming interface. To make sure that recipe takes advantage of regional policy-based routing. The very fact that the router makes the packets also presents it an essential benefit considering the fact that it does not have to take into consideration any DLSw packets that may just transpire to go through.

The benefits on the newer class-map way are not apparent in this particular instance, but among the first great features seems in order for you to work with the more fashionable DSCP tagging scheme. As the older policy-based routing method will not immediately support DSCP, you've got to pretend it by setting each the IP Precedence and also TOS individually as follows.

Router(config)#route-map serialftp-rtmap permit 10
Router(config-route-map)#match ip address 115
Router(config-route-map)#set ip precedence immediate
Router(config-route-map)#set ip tos max-throughput

In this case, the packet will wind up with an IP Precedence value of immediate, or 2 (010 in binary), and TOS of max-throughput, or 4 (0100 in binary).

Doing the same thing with the class-map method is much more direct:

Router(config)#policy-map serialftppolicy
Router(config-pmap)#class serialftpclass
Router(config-pmap-c)#set ip dscp af21

Class-maps may even be advantageous later on in such a chapter after we discuss class-based weighted reasonable queuing and class-based targeted traffic shaping.
It is crucial to notice that all through this whole example, we have now only set a particular price into your packet's TOS or DSCP discipline. This, by by itself, would not have an affect on how the packet is forwarded by means of the network. To carry out that, you must be certain that as each router inside network forwards these marked packets, the interface queues will react appropriately to this data.

Finally, we should always notice that as this recipe demonstrates two advantageous tactics of marking packets, implementing Dedicated Accessibility Fee (Motor vehicle) benefits. Car tends to become a lot more efficient on greater speed interfaces.

Post in CCIE R&S | Comments Closed