I digress

The point is that I just today received an email from an aspiring dual CCIE from Africa. This engineer had to sell his TV and entertainment systems to pay for a lab. Taking this guy’s money was like stealing candy from a baby. I urge he gets it back but the system works as it does and I have no real influence, but you do. You the CCIEs and Cisco engineers out there in the world can wag the dog. You are a mighty big dog that influences the purchasing decisions of corporations that influence commerce around the world. You the lowly Cisco network engineers. It seems some of you have been heard because I hev heard it through the grapevine that Cisco is lowering the price for the CCIE labs to $1,000. This is a great next step after the Waiver and the Core Knowledge Questions (OEQs) have passed into history.

Kudos, Props and Thanks

Really. I was so excited I had a Margarita with lunch. Kudos Learning at Cisco, Props management teams that took this challenge on and Thanks to the rest of you who made this possible. I have even read that this was going to be announced at Cisco Live in June. Wow, it’s only May and we are talking about it already.

CCIE Population Numbers

At a time when the numbers are on the decline and published and unpublished efforts have been made to keep the certifications pure this is a great move. Hello, I am a recruiter and given bodies to recruit I get all pimply and excited. So getting the numbers up using an equation that includes discounts is a recipe for success.

So let’s all look forward to the announcement in June at Cisco Live – Networkers. See you there!

This lab is part of my new  Boot Camp 2.0  work book, the idea of this work
book is to explore every option within every item in the blueprint, this lab
covers RIPv2 ONLY.

The combination of my  Advanced CCIE Routing and Switching 2.0 ,
Troubleshooting Work Book, which contains 10 six-eight hour Troubleshooting
labs and my new  Boot Camp 2.0  work book will increase your chances of
passing this  ridiculously easy  certification.

How long does it take to complete this lab?

It all depends on how prepared you are, if you NOT prepared and you are at a
CCNP level it can take up to 7 hours to complete, some students don t even
complete the entire lab. But if you are almost ready, it should NOT take you
longer than 4 hours to complete this lab.

How should I do this lab?

My recommendation:

- You have a topology.doc file, print the file and look at the topology
as you configure the lab.
- You have a  initial-config  directory, which contains all the initial
configuration files, open the  RIPv2-Init.txt  and copy and paste the
configuration onto the routers and begin the lab.
- You should use the  Questions.pdf  when you are configuring the lab,
and before you move on to another task, read the  Questions-Answers.pdf
and
compare the answers.

Once you complete this lab, you should have confidence about your knowledge
of this routing protocol.

Please do not hesitate to share this lab with friends or even share it on
your blog (If you have one).

Download it here

R4#sh mpls ldp discovery
Local LDP Identifier:
4.4.4.4:0
Discovery Sources:
Interfaces:
Ethernet0/0 (ldp): xmit/recv
LDP Id: 6.6.6.6:0; no host route

If your action is permit then everything else is going to be denied, if your action is deny then everything elsewould be permitted.

Sw1(config)#ip igmp profile 6

Sw1(config-igmp-profile)#permit

Sw1(config-igmp-profile)#range 224.1.1.1

Sw1(config-igmp-profile)#end

Sw1(config)#do show ip igmp profile 6

IGMP Profile 6

permit

range 224.1.1.1 224.1.1.1

Sw1(config)#int f0/3

Sw1(config-if)#ip igmp filter 6

Objective

• PPPoE connection between R1 and R2.
• CHAP authentication is to be used.
• R2 should provide R1 an address via DHCP.

Configuration

We will start on R1. A dialer interface is needed and the FastEthernet interface needs to be associated with the same dialer pool. Under the dialer we can configure PPP options such as authentication and how the interface will learn its IP address. PPP commands will not be available until you specify the encapsulation as PPP on the dialer interface,

R1(config)#username R2 password pppoe-lab

R1(config)#int f0/0

R1(config-if)#pppoe-client dial-pool-number 1

R1(config)#int dialer 1

R1(config-if)#dialer-group 1

R1(config-if)#dialer pool 1

R1(config-if)#ppp auth?

% Unrecognized command

R1(config-if)#encapsulation ppp

R1(config-if)#ppp authen chap

R1(config-if)#ip address dhcp

R2, the server in this example, will not use a dialer interface. Instead it uses a virtual-template and bb-group configuration. PPP options are configured under the virtual template, the virtual-template is assigned to the bba-group, and the bba-group is attached to the FastEthernet interface. BBA is an abbreviation for Broadband access.

R2(config)#username R1 password pppoe-lab

R2(config)#ip dhcp pool R1

R2(dhcp-config)#network 192.168.1.0 /24

R2(dhcp-config)#exit

R2(config)#interface virtual-template 1

R2(config-if)#ip address 192.168.1.2 255.255.255.0

R2(config-if)#encap ppp

R2(config-if)#ppp authentication chap

R2(config-if)#exit

R2(config)#bba-group pppoe global

R2(config-bba-group)#virtual-template 1

R2(config-bba-group)#int f0/0

R2(config-if)#pppoe enable group globa

Debugging on R1 gives the following.

R1#debug pppoe events

PPPoE protocol events debugging is on

Aug  3 14:30:35.551:  Sending PADI: Interface = FastEthernet0/0

Aug  3 14:30:35.567: PPPoE 0: I PADO  R:c201.0bfc.0000 L:c200.0bfc.0000 Fa0/0

Aug  3 14:30:37.599:  PPPOE: we’ve got our pado and the pado timer went off

Aug  3 14:30:37.599: OUT PADR from PPPoE Session

Aug  3 14:30:37.615: PPPoE 3: I PADS  R:c201.0bfc.0000 L:c200.0bfc.0000 Fa0/0

Aug  3 14:30:37.619: IN PADS from PPPoE Session

Aug  3 14:30:37.631: %DIALER-6-BIND: Interface Vi1 bound to profile Di1

Aug  3 14:30:37.635: PPPoE: Virtual Access interface obtained.

Aug  3 14:30:37.635: PPPoE : encap string prepared

Aug  3 14:30:37.639: [0]PPPoE 3: data path set to Virtual Acess

Aug  3 14:30:37.659: %LINK-3-UPDOWN: Interface Virtual-Access1, changed state to up

Aug  3 14:30:41.051: %LINEPROTO-5-UPDOWN: Line protocol on Interface Virtual-Access1, changed state to up

Aug  3 14:30:49.175: %DHCP-6-ADDRESS_ASSIGN: Interface Dialer1 assigned DHCP address 192.168.1.3, mask 255.255.255.0, hostname R1

From the above output we can see the process follows the RFC pretty well. The client broadcasts a PPPoE Active Discovery Initiation (PADI) packet to learn of any servers on the network. R2 responds with a unicast PPPoE Active Discovery Offer (PADO). This packet contains a tag that the client uses to associate with the proper request. After receiving the PADO, the client sends a PPPoE Active Discovery Request (PADR) packet, which is unicast top the server. The server responds with a PPPoE Active Discovery Session-confirmation (PADS) packet and PPP negotiation begins.

Here are some verification commands on each device:

R1#sho pppoe session

1 client session

Uniq ID  PPPoE  RemMAC          Port                    VT  VA         State

SID  LocMAC                                      VA-st

N/A      3  c201.0bfc.0000  Fa0/0                  Di1  Vi1        UP

c200.0bfc.0000                              UP

R2#sho pppoe session

1 session  in LOCALLY_TERMINATED (PTA) State

1 session  total

Uniq ID  PPPoE  RemMAC          Port                    VT  VA         State

SID  LocMAC                                      VA-st

3      3  c200.0bfc.0000  Fa0/0                    1  Vi2.1      PTA

c201.0bfc.0000                              UP

Some final things to remember

• Configure dialer interface in client
• Dialer interface contains ppp and addressing options
• Ethernet interface must belong to same dialer pool
• Configure virtual-template and bba-group on server
• Virtual-template contains ppp options and IP address
• BBA-group is configured under the Ethernet interface

router os 1
distance 171 <ROUTER-ID> <WILDCARD MASK> Accesslist allows you to selectively change the AD for any route in OSPF.!!!

Now the summarized route at R2 will have a metric of X+1. Without summarization it has a metric of X.!

Tony Bradley :

The Google Chrome OS is generating excitement, but it doesn’t seem to be compelling enough to be worth the hype. Here are five reasons Chrome will ultimately fail to impress.

Yesterday Google hosted a press event at its Mountain View campus to reveal a first glimpse at the Chrome OS. The excitement around the operating system has led to rampant rumors and speculation, but I question whether the Chrome OS is really worth any of this hype.

Google is Google. It has a Midas touch when it comes to web-based applications and services so its easy to get wrapped up in anticipation about a web-centric operating system from Google. Here are five reasons Chrome won’t live up to the hype.

Editor’s note: Dide3d admin Dejoe John takes an alternate point of view in his Today@ blog “Five Reasons the Google OS will Succeed“. Think they are both wrong? We’d love to hear your thoughts in the comments)

1. Not everything runs in the cloud. I know Google has a web-centric, cloud-computing perspective on the world, but not everything runs from the cloud. Sure, Picassa and Flickr have some photo editing capabilities, but they’re not Adobe Photoshop.

That is just one example, but the point is that there are applications that pretty much have to be run locally. An operating system that is essentially just a web browser on steroids designed to run on low-end netbook hardware will not be able to fill that need.

2. The cloud isn’t always available. In order to run all of your applications from the cloud, you have to be connected to the cloud. Wi-Fi connections are becoming more ubiquitous, but there are still plenty of places I go where there is no Wi-Fi available.

An airplane is a good example. Airlines are beginning to implement wireless network availability in-flight, but usually for a fee. That basically renders a Chrome OS netbook useless while flying unless you cave and pay the exorbitant airline access fees.

3. Games. One of the driving forces behind PC hardware development and PC sales is gaming. Nobody needs a $750 graphics card to use Microsoft Office, and a 5.1 surround sound speaker system is a little overkill for checking email.

Sure, there are games on the web. Thousands of them. Facebook users waste spend weeks of time playing Mafia Wars and Farmville. But, Farmville is no Spore. Hardcore gamers want the raw horsepower that a PC provides.

4. Chrome web browser. Google’s Chrome web browser has been around for awhile. It has received some good reviews and has experience a relative degree of success in a crowded browser market.

That is admirable, but the Chrome web browser hasn’t exactly caught fire. It isn’t steamrolling Internet Explorer, or even Firefox, to capture browser market share. If the world isn’t tripping over itself to get the web browser, it seems safe to assume we also won’t flock to drop our Windows or Mac based hardware for a netbook running a glorified version of the browser we weren’t using in the first place.

5. We can do most of that now for free. Google doesn’t intend to offer the Chrome OS as a free application like most things Google. The plan is to make the Chrome OS available pre-installed on netbook hardware by the 2010 holiday season.

We can already do most, if not all, of what Chrome OS promises to deliver. Using a Windows 7 or Linux-based netbook, users can simply not install anything but a web browser and connect to the vast array of Google products and other web-based services and applications.

Netbooks have been successful at capturing the low-end PC market, and they provide a web-centric computing experience today. I am not sure why we should get excited that a year from now we’ll be able to do the same thing, but locked into doing it from the fourth-place web browser.

The Chrome OS is half Linux and half Chrome web browser. Netbooks built on the Chrome OS will basically be web appliances running an operating system that is really just a web browser on steroids.

Google is virtually synonymous with the web, so its hard not to get excited. The Chrome OS may have something to offer the netbook audience, but it is not a threat to existing desktop operating systems at all.

My Dide3d counterpart Dejoe John seems to agree that the Chrome OS will essentially be a niche operating system. Dejoe feels, though, that Google is not trying to take over the operating system market and that, relative to what the OS is intended to be, Chrome will be a success. Perhaps.

If it didn’t have the word ‘Google’ at the front, nobody would care and most people would simply dismiss the effort. Chrome OS will be little more than a niche product and it begs the question ‘why bother?’