Posted by Peter Kurdziel on November 7, 2008
*Mar 1 03:25:26.251: BGP: 183.1.17.7 bad OPEN, remote AS is 100, expected 200
*Mar 1 03:25:26.251: BGP: 183.1.17.7 went from OpenSent to Closing
*Mar 1 03:25:26.251: %BGP-3-NOTIFICATION: sent to neighbor 183.1.17.7 2/2 (peer in wrong AS) 2 bytes 0064 FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF 002D 0104 0064 00B4 9601 0707 1002 0601 0400 0100 0102 0280 0002 0202 00
*Mar 1 03:25:26.255: BGP: 183.1.17.7 send message type 3, length (incl. header) 23
*Mar 1 03:25:26.363: BGP: 183.1.17.7 local error close after sending NOTIFICATION
*Mar 1 03:25:26.367: BGPNSF state: 183.1.17.7 w
Rack1R1#ent from nsf_not_active to nsf_not_active
*Mar 1 03:25:26.367: BGP: 183.1.17.7 went from Closing to Idle
*Mar 1 03:25:26.367: BGP: 183.1.17.7 closing
*Mar 1 03:25:27.383: BGP: 183.1.17.7 went from Idle to Active
*Mar 1 03:25:27.395: BGP: 183.1.17.7 open active delayed 27694ms (35000ms max, 28% jitter)
Rack1R1#
*Mar 1 03:25:55.091: BGP: 183.1.17.7 open active, local address 183.1.17.1
*Mar 1 03:25:55.275: BGP: 183.1.17.7 went from Active to OpenSent
TYPO WAS CORRECTED
*Mar 1 03:25:55.279: BGP: 183.1.17.7 sending OPEN, version 4, my as: 200, holdtime 180 seconds
*Mar 1 03:25:55.287: BGP: 183.1.17.7 send message type 1, length (incl. header) 45
*Mar 1 03:25:55.355: BGP: 183.1.17.7 rcv message type 1, length (excl. header) 26
*Mar 1 03:25:55.359: BGP: 183.1.17.7 rcv OPEN, version 4, holdtime 180 seconds
*Mar 1 03:25:55.359: BGP: 183.1.17.7 rcv OPEN w/ OPTION parameter len: 16
*Mar 1 03:25:55.363: BGP: 183.1.17.7 rcvd OPEN w/ optional parameter type 2 (Capability) len 6
*Mar 1 03:25:55.363: BGP: 183.1.17.7 OPEN has CAPABILITY code: 1, length 4
*Mar 1 03:25:55.367: BGP: 183.1.17.7 OPEN has MP_EXT CAP for afi/safi: 1/1
*Mar 1 03:25:55.367: BGP: 183.1.17.7 rcvd OPEN w/ optional parameter type 2 (Capability) len 2
*Mar 1 03:25:55.367: BGP: 183.1.17.7 OPEN has CAPABILITY code: 128, length 0
*M
Rack1R1#ar 1 03:25:55.367: BGP: 183.1.17.7 OPEN has ROUTE-REFRESH capability(old) for all address-families
*Mar 1 03:25:55.367: BGP: 183.1.17.7 rcvd OPEN w/ optional parameter type 2 (Capability) len 2
*Mar 1 03:25:55.367: BGP: 183.1.17.7 OPEN has CAPABILITY code: 2, length 0
*Mar 1 03:25:55.367: BGP: 183.1.17.7 OPEN has ROUTE-REFRESH capability(new) for all address-families
BGP: 183.1.17.7 rcvd OPEN w/ remote AS 200
*Mar 1 03:25:55.367: BGP: 183.1.17.7 went from OpenSent to OpenConfirm
*Mar 1 03:25:55.367: BGP: 183.1.17.7 went from OpenConfirm to Established
*Mar 1 03:25:55.367: %BGP-5-ADJCHANGE: neighbor 183.1.17.7 Up
Solution: typo on switch.
This is some good stuff here showing the BGP message states. (see the bold)
Posted in BGP, Routing & Switching Lab | Leave a Comment »
Posted by Peter Kurdziel on November 7, 2008
Please review the Lab Exam Overview for general information about the lab exam. The information below is meant to help you prepare for the lab exam.
STUDY TIPS
Assessing Strengths
Using the content blueprint, determine your experience and knowledge in the major topic areas. For areas of strength, practicing for speed should be your focus. For weak areas, you may need training or book study in addition to practice.
Study Materials
Choose lab materials that provide configuration examples and take a hands-on approach. Look for materials that are approved or provided by Cisco and its Learning Partners.
Hands-On Practice
Build and practice lab scenarios on a per topic basis. Go beyond the basics and practice additional features. Learn the show and debug commands along with each topic. If a protocol has multiple ways of configuring a feature, practice all of them.
Cisco Documentation CD
Make sure you can navigate the Cisco documentation CD with confidence because this is the only resource you will be allowed during the lab. Make the CD part of your regular study; if you are familiar with it, you can save time during the exam. As of March 2006, the documentation can only be navigated using the index; the search function has been disabled.
Home Labs
Although acquiring a personal home lab is ideal, it can be costly to gather all the equipment you will need. For the hardware devices that are costly to obtain, you may be able to rent the equipment online at a more reasonable cost.
TEN TIPS FOR TAKING THE LAB EXAM
- Read the entire exam first and check for addressing issues. Do not skip any details or sections.
- Manage your time. Make a plan to cover all the sections in the time provided. Work out how much time you will spend on each section, keeping in mind the point value of the questions. Don’t forget to allow time at the end to verify your solutions.
- Clarify the requirements of each question. Don’t assume requirements that aren’t mentioned in the question. During the lab, if you are in any doubt, verify your understanding of the question with the proctor.
- Do each question as a unit. Configure and verify before moving to the next question. You may want to redraw the topology with all the details available. This will help you visualize and map the network.
- Troubleshoot. You must know how to troubleshoot using the tools available. Although troubleshooting is important, don’t lose too much time working on a 2- or 3-point question. If you’re caught off-guard by an unfamiliar topic, don’t let it absorb too much time. Work on the things you are more comfortable with and go back to difficult items later.
- Keep a list. During the exam, make notes on configurations and settings as you move through the exam. Make a separate list for items you have not been able to address or where you have not achieved the desired result which you’ll need to revisit.
- Test your work. Never rely on a configuration done in the early hours of the exam. There is a possibility that an item you configured a few sections earlier can become broken and non-functional. Keep in mind that points are awarded for working configuration only.
- Save your configurations often.
- Don’t make any drastic changes in the last half hour of the exam.
- Speed is vital on the exam. Review and practice core material the week before the exam to ensure you can move quickly through the less challenging questions.
Reference: http://www.cisco.com/web/learning/le3/ccie/rs/lab_exam_tips.html
Posted in Routing & Switching Lab | Leave a Comment »
Posted by Peter Kurdziel on November 7, 2008
Reasons why people Fail the Lab Exam!
Reason 1: “I was on no/little sleep!”
• Nerves
• Caffeine
• Abnormal routine
• Cramming
• Abnormal environment
Reason 2: “I ran out of time!”
• Practice, Practice, Practice
• Speed drills
• Overall strategy approach
• Specific strategies
• Adherence to time management practices
Reason 3: “The proctor was not helpful at all!”
• Be Nice!
• Demonstrate knowledge
• Be specific
• Communicate you are not looking for an answer – request clarification
• Try another – try again
Reason 4: “I got tons of topic XYZ!”
• FOCUS ON YOUR WEAK AREAS!!!!!!!
Reason 5: “Too stressed out at that point in my life!”
• Stress mitigation techniques
• Rescheduling the lab
Reason 6: “I was physically sick for the lab!”
• Stress mitigation techniques
Reason 7: “I had absolutely no chance to pass that lab!”
• Formalized CCIE training!
Reason 8: “I HAVE NO IDEA WHY I FAILED!!!!”
• Task misinterpretation
• Poor verification techniques
reference:http://freeiestuff.com/fail.aspx
Posted in Routing & Switching Lab | Leave a Comment »
Posted by Peter Kurdziel on November 7, 2008
I ran into a problem with a neightbor stuck in Init.
The problem was when I loaded my lab in GNS3. I had some dynamic frame-relay mappings even through I had no shut that off in my config. I cleared them with clear frame in and made sure my configs were correct. The neighbor came up and all is well.
For some reason GNS3 is pulling an old config from somewhere. I noticed lots of weird stuff with GNS3/dynamips. I spent hours tweaking things and I think I have it working the way it’s supposed to now.
Posted in Routing & Switching Lab | Leave a Comment »
