<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>Ccie - Tag - Fryguy's Blog</title><link>https://hugo.fryguy.net/tags/ccie/</link><description>Ccie - Tag - Fryguy's Blog</description><generator>Hugo -- gohugo.io</generator><language>en</language><lastBuildDate>Thu, 09 Jun 2022 12:42:00 +0000</lastBuildDate><atom:link href="https://hugo.fryguy.net/tags/ccie/" rel="self" type="application/rss+xml"/><item><title>Cisco Live 2022 – Are you ready?</title><link>https://hugo.fryguy.net/2022/06/09/cisco-live-2022-are-you-ready/</link><pubDate>Thu, 09 Jun 2022 12:42:00 +0000</pubDate><author>Fryguy</author><guid>https://hugo.fryguy.net/2022/06/09/cisco-live-2022-are-you-ready/</guid><description><![CDATA[<div class="wp-block-image">
  
</div>
<p>Soon, many of us will be on an airplane heading to Las Vegas for Cisco Live 2022. So I felt that it might be good to put out some final information before we head out. Below you will find some info on the Cisco Events App, Health and Safety info, as well as NetVet reception updates.</p>
<p>Cisco recently updated its Cisco Events application for Cisco Live 2022, this is a must-have application for an attendee. This application is your go-to for everything CIsco Live, as you can see from the images below, it has all the relevant information you need – the Session Catalog, the All Sessions section has your Schedule for the sessions you have signed up for as well.</p>]]></description></item><item><title>Could the Cisco CCIE lab in RTP be moving? CONFIRMED!</title><link>https://hugo.fryguy.net/2018/11/06/could-the-cisco-ccie-lab-in-rtp-be-moving/</link><pubDate>Tue, 06 Nov 2018 13:00:01 +0000</pubDate><author>Fryguy</author><guid>https://hugo.fryguy.net/2018/11/06/could-the-cisco-ccie-lab-in-rtp-be-moving/</guid><description><![CDATA[<div class="wp-block-image">

</div>
<p class="has-vivid-red-color has-text-color">
  <strong><em>Let me preface this post by saying that this post is not <g class="gr_ gr_6 gr-alert gr_gramm gr_inline_cards gr_run_anim Grammar only-ins replaceWithoutSep" id="6" data-gr-id="6">Cisco</g> official nor sponsored.&nbsp; This post should be taken as speculation and I am presenting what I have been able to put together.&nbsp; Until Cisco has announced something official, take everything I have here with a grain of salt and do not assume it as fact.&nbsp; If something changes I will update the post as appropriate.</em></strong>
</p>
<p class="has-vivid-red-color has-very-light-gray-background-color has-text-color has-background">
  <strong><a href="#Update">Jump to updates&nbsp; &#8211; SJC too?</a></strong><br />11/12 &#8211; New Cisco Learning thread on this topic
</p>
<p>Adding the latest updates to the top.</p>
<p>In a series of tweets today from @LearningatCisco they have confirmed today (14-Nov-2018) that RTP and SJC are transitioning to mobile test sites and the new home of the lab is Richardson, TX. The last on-sites dates for CCIE testing in SJC is 28-Nov-2018 and for RTP is 07-Dec-2018.</p>
<blockquote class="wp-block-quote is-layout-flow wp-block-quote-is-layout-flow">
  <p>
    Effective immediately, the last on-site testing date before San Jose, CA CCIE lab is transitioned to a mobile test site is November 28, 2018. For RTP, NC the last on-site testing date is December 7, 2018.<br />— LearningatCisco (@LearningatCisco) <a href="https://twitter.com/LearningatCisco/status/1062691870562758658?ref_src=twsrc%5Etfw">November 14, 2018</a><br />
  </p>
  <p>
    Cisco is adding a new, permanent <a href="https://twitter.com/hashtag/CCIE?src=hash&ref_src=twsrc%5Etfw">#CCIE</a> lab in Richardson, TX. RTP, NC and San Jose, CA will now become mobile test sites, adding to the 40+ locations we offer globally for convenient access to lab testing, <a href="https://t.co/mzGeE7DqBE">https://t.co/mzGeE7DqBE</a>. Scroll to News section.
  </p>
  <p>
    While the CCIE Lab in Richardson, TX, is not on the lab locations page it is an on-site testing facility as of now. Any available seats can be seen on the schedule, please check current availability by logging in to the CCIE Online Lab Scheduler.<br />— LearningatCisco (@LearningatCisco) <a href="https://twitter.com/LearningatCisco/status/1062692121508044803?ref_src=twsrc%5Etfw">November 14, 2018</a><br />
  </p>
  <p>
    <a href="https://twitter.com/LearningatCisco" target="_blank" rel="noreferrer noopener" aria-label="Effective immediately, the last on-site testing date before San Jose, CA CCIE lab is transitioned to a mobile test site is November 28, 2018.  For RTP, NC the last on-site testing date is December 7, 2018.
— LearningatCisco (@LearningatCisco) November 14, 2018
<p>Cisco is adding a new, permanent #CCIE lab in Richardson, TX.  RTP, NC and San Jose, CA will now become mobile test sites, adding to the 40+ locations we offer globally for convenient access to lab testing, <a href="https://t.co/mzGeE7DqBE" target="_blank" rel="noopener noreffer ">https://t.co/mzGeE7DqBE</a>. Scroll to News section.
While the CCIE Lab in Richardson, TX, is not on the lab locations page it is an on-site testing facility as of now.  Any available seats can be seen on the schedule, please check current availability by logging in to the CCIE Online Lab Scheduler.
— LearningatCisco (@LearningatCisco) November 14, 2018</p>
<p>Tweets from @LearningatCisco  (opens in a new tab)&quot;&gt;Tweets from @LearningatCisco</a></p>
  </p>
</blockquote>
<p><strong>— END OF UPDATE ABOVE, now back to regular post.</strong></p>
<p>Last night I saw a post on my Facebook social media feed about that CCIE lab in RTP that caught my attention.  The post was about the CCIE lab in RTP moving at the end of December 2018 to Richardson, TX! </p>
<div class="wp-block-image">

</div>
<p>I had a hard time believing this, so I did some quick research that actually leads me to some job postings for a CCIE Proctor in Richardson, TX.  Both of these posting are no longer live, so I have included links to their cached copies.</p>]]></description></item><item><title>10 Year CCIE – My Reflection</title><link>https://hugo.fryguy.net/2018/11/05/10-year-ccie-my-reflection/</link><pubDate>Mon, 05 Nov 2018 13:30:56 +0000</pubDate><author>Fryguy</author><guid>https://hugo.fryguy.net/2018/11/05/10-year-ccie-my-reflection/</guid><description><![CDATA[<div class="wp-block-image">

</div>
<p>How time flies – it is now over 10 years ago that I earned my Cisco CCIE R&amp;S number of 22061.  It was the culmination of failing the lab quite a few times, trying to study as hard as I could, and had the pressure that my CCIE written prequalification was going to expire soon.  I want to do a quick post with my reflection of the CCIE, what it means to me, what it has done for me,  and what I see with it now.</p>
<p>When I first earned my CCIE, like many people out there I suspect, my head was bigger than my shoulders could carry and I would let everyone know that I am a CCIE.   Looking back on that I realize how much of an arse I probably sounded (and may have acted) like.  _Lesson learned – just because you have a cert does not mean you need to tell everyone. My advice to you – be proud of what you have accomplished, but don’t let it get to you.  _</p>]]></description></item><item><title>CCIE Recertification Continuing Education Review</title><link>https://hugo.fryguy.net/2018/04/13/ccie-recertification-continuing-education-review/</link><pubDate>Fri, 13 Apr 2018 19:04:52 +0000</pubDate><author>Fryguy</author><guid>https://hugo.fryguy.net/2018/04/13/ccie-recertification-continuing-education-review/</guid><description><![CDATA[<p><a href="https://www.cisco.com/c/en/us/training-events/training-certifications/certifications/expert.html" target="_blank" rel="noopener noreffer "></a><br>
Way back in 2008  I passed the CCIE R&amp;S lab to obtain my CCIE #22061.  Over the past years, I have taken recertification written exams including the CCIE Voice, CCIE Service Provider, CCIE R&amp;S, as well as the CCDE written tests to maintain active CCIE status.  Last June, Cisco announced a change to the recertification procedure and made available the ability to use a <a href="/2017/06/06/cisco-ccieccde-recertification-update/" target="_blank" rel="noopener noreferrer">Continuing Education Program</a> as well to the standard written tests. This time around I chose to take advantage of that program to recertify and wanted to share my results and experiences with the process.<br>
To access the Continuing Education Program dashboard for your certification, you just need to navigate to <a href="https://ce.cisco.com/#/dashboard" target="_blank" rel="noopener noreffer ">https://ce.cisco.com/#/dashboard.</a> Once there you will be able to see your current certification status (CCIE and any other certifications associated with your account).  To renew your CCIE certification, you are required to earn 100 credits and submit the appropriate proof of attendance.  For more FAQ information, see the Cisco FAQ at <a href="https://fryguy.me/2sc8hXG" target="_blank" rel="noopener noreffer ">https://fryguy.me/2sc8hXG</a>.<br>
I took three courses, all online and delivered by Cisco Learning Systems,  in order to recertify:</p>]]></description></item><item><title>Cisco CCIE/CCDE Recertification Update</title><link>https://hugo.fryguy.net/2017/06/06/cisco-ccieccde-recertification-update/</link><pubDate>Tue, 06 Jun 2017 12:19:52 +0000</pubDate><author>Fryguy</author><guid>https://hugo.fryguy.net/2017/06/06/cisco-ccieccde-recertification-update/</guid><description><![CDATA[  
This morning while looking at new blog posts I came across one that grabbed me.  For forever and a day the Cisco CCIE recertification policy was that you are required to take a CCIE/CCDE level written exam every two years to stay active.  Well, reading Daniel&#8217;s blog over at <a href="http://lostintransit.se/2017/06/06/certification-major-news-expert-level-recertification/" target="_blank" rel="noopener noreferrer">LostInTransit</a>, it seems that has finally changed.  
Seems today (6/6/17) Cisco has updated their recertification policy to also include a Continuing Education Program where you earn credits that will count towards recertification. This brings their recertification policy in line with other certification tracks (<a href="https://www.isc2.org/cissp/default.aspx" target="_blank" rel="noopener noreferrer">CISSP</a>, <a href="http://www.isaca.org/Certification/CISA-Certified-Information-Systems-Auditor/Pages/Maintain-Your-CISA.aspx" target="_blank" rel="noopener noreferrer">CISA</a>, ISC2, etc.).  
Reading the Cisco <a href="https://learningnetwork.cisco.com/community/certifications/cisco-continuing-education-program" target="_blank" rel="noopener noreferrer">Continuing Education Program </a>site, it seems that the program is based on three principles &#8211; Flexibility, Diversity, and Integrity.  Flexibility means that there are now additionals ways for CCIE/CCDE to recertify besides the written exams.  Diversity is by allowing individuals to take approved courses and training, as well as Cisco Live offerings.  Integrity is based on having Cisco authorized providers to validate the class and credits that a person takes.  
Here is a bulleted list of the information that I have been able to find:]]></description></item><item><title>Cisco Exam Policy Changes and Cost Increases</title><link>https://hugo.fryguy.net/2014/06/24/cisco-exam-policy-changes-and-cost-increases/</link><pubDate>Tue, 24 Jun 2014 18:15:33 +0000</pubDate><author>Fryguy</author><guid>https://hugo.fryguy.net/2014/06/24/cisco-exam-policy-changes-and-cost-increases/</guid><description><![CDATA[<p align="center">
  
</p>
<p> <br>
There has been some talk on the twitter-verse and at Cisco Live around some of the changes that Cisco is making to the CCIE/DE written and lab policies.  Last month they posted those changes to their <a href="http://www.cisco.com/web/learning/exams/policies.html#~Lab" target="_blank" rel="noopener noreferrer">Certification Exam Policies website</a> to let everyone know and read.  The ones that are key to CCIE/DE candidates (and some will be effective August 2, 2014) are:<br>
<strong>Written:</strong></p>
<ul>
<li>Candidates who fail the CCIE/DE written must want 15 calendar days, beginning the day after the fail, before retaking the exam</li>
<li>Once passed, you cannot retake the same written exam within 180 days</li>
<li>Candidates may attempt the CCIE/DE written exam up to four (4) times per rolling calendar year.</li>
</ul>
<p><strong>Lab (here is the big one):</strong></p>
<ul>
<li>Candidate must wait 30 days between CCIE lab attempts (30 days starts the day after the failed attempt)</li>
<li>For your 1<sup>st</sup>  attempt there is no wait time.</li>
<li>For your 2<sup>nd</sup>  attempt, there is a 30 day wait time</li>
<li>For your 3<sup>rd</sup>, 4<sup>th</sup>, and 5<sup>th</sup> attempt, there is a 90 wait time between each</li>
<li>For your 6<sup>th</sup> , 7<sup>th</sup>  and onward, the there is a 180 day wait time between each.</li>
</ul>]]></description></item><item><title>Cisco CSR1000v For Home Labs</title><link>https://hugo.fryguy.net/2013/12/27/cisco-csr1000v-for-home-labs/</link><pubDate>Fri, 27 Dec 2013 14:00:40 +0000</pubDate><author>Fryguy</author><guid>https://hugo.fryguy.net/2013/12/27/cisco-csr1000v-for-home-labs/</guid><description><![CDATA[<p align="center">
  
</p>
<p>I have been using the Cisco CSR1000V for my home lab setup for a little bit now.  There have been some questions on how to set this up for a home lab and I figured I would cover how I am using it.<br>
For this post, here is what we are going to build –  a three (3) node CSR1000V network and three (3) vSwitch Networks to connect the CSR1000Vs together.  We will also configure the CSR1000V to have connectivity back to the “home production” network so that we can SSH/Telnet to these routers when we are labbing.<br>
</p>
<h2 id="obtaining-the-csr1000v-router-software">Obtaining the CSR1000V Router Software</h2>
<p>To obtain the Cisco CSR1000V you need to download it from Cisco at this <a href="http://www.cisco.com/en/US/products/ps12559/" target="_blank" rel="noopener noreferrer">LINK</a> and click on the Download software as seen circled below</p>]]></description></item><item><title>IOS XR – HSRP and VRRP</title><link>https://hugo.fryguy.net/2012/10/08/ios-xr-hsrp-and-vrrp/</link><pubDate>Mon, 08 Oct 2012 12:29:31 +0000</pubDate><author>Fryguy</author><guid>https://hugo.fryguy.net/2012/10/08/ios-xr-hsrp-and-vrrp/</guid><description><![CDATA[<p><a href="/wp-content/uploads/2012/09/iosxrfryguy-8.jpg" rel=""></a><br>
Next Hop Resolution Protocol comes in two fashions on the IOS XR.  The first is Cisco proprietary and called Hot-Standby Router Protocol or HSRP and the other is the industry standard called Virtual Router Redundancy Protocol or VRRP.<br>
This is something that many customers use in order to maintain the availability of a default gateway on the network.  If your customer uses a static route to a next hop, you might be using this as well.<br>
Like everything else with IOS XR, NHRP is handled a little differently.  With IOS, you configure your standby commands under the interfaces; in IOS XR you use ROUTER HSRP or Router VRRP.<br>
For this lab we will use interface Te0/1/0/0 and a subnet of 150.1.12.0/24.<br>
First up R1:<br>
<span style="color: #0000ff;">RP/0/RSP0/CPU0:R1(config)#<span style="color: #ff0000;">int tenGigE 0/1/0/0         </span></span><br>
<span style="color: #0000ff;">RP/0/RSP0/CPU0:R1(config-if)#<span style="color: #ff0000;">ip add 150.1.12.1/24</span></span><br>
<span style="color: #0000ff;">RP/0/RSP0/CPU0:R1(config-if)#<span style="color: #ff0000;">no shut</span></span><br>
<span style="color: #0000ff;">RP/0/RSP0/CPU0:R1(config-if)#<span style="color: #ff0000;">commit </span></span><br>
<span style="color: #0000ff;">RP/0/RSP0/CPU0:R1(config-if)#</span><br>
Now R2:<br>
<span style="color: #0000ff;">RP/0/RSP0/CPU0:R2(config)#<span style="color: #ff0000;">int tenGigE 0/1/0/0</span></span><br>
<span style="color: #0000ff;">RP/0/RSP0/CPU0:R2(config-if)#<span style="color: #ff0000;">ip add 150.1.12.2/24</span></span><br>
<span style="color: #0000ff;">RP/0/RSP0/CPU0:R2(config-if)#<span style="color: #ff0000;">no shut</span></span><br>
<span style="color: #0000ff;">RP/0/RSP0/CPU0:R2(config-if)#<span style="color: #ff0000;">commit</span></span></p>]]></description></item><item><title>IOS XR – MPLS VPN</title><link>https://hugo.fryguy.net/2012/10/02/ios-xr-mpls-vpn/</link><pubDate>Tue, 02 Oct 2012 12:41:26 +0000</pubDate><author>Fryguy</author><guid>https://hugo.fryguy.net/2012/10/02/ios-xr-mpls-vpn/</guid><description><![CDATA[<p><a href="/wp-content/uploads/2012/09/iosxrfryguy-8.jpg" rel=""></a><br>
Next up is MPLS VPN; actually VPNv4 routes are what these actually are since we are only passing IPv4 traffic in this example.<br>
So we have this diagram below – CE1 and CE2 are the customer routers and both are running OSPF in Area 0.  They need to talk to each other but do not have a direct connection available, so they have contracted us to provide connectivity via MPLS between them.  What we will now do is build a pseudo MPLS network between PE1 and PE2, establish an iBGP peering, create the associated customer VRF and then peer with the customer via OSPF Area 0.</p>
<p style="text-align: center;">
  <a href="/wp-content/uploads/2012/09/Network.jpg"></a>
</p>
<p>So, first up lets configure CE1 using an IP of 10.3.3.3/32 for the loopback and 10.1.13.3/24 for the link facing PE1.<br>
<span style="color: #0000ff;">CE1#<span style="color: #ff0000;">conf t</span></span><br>
<span style="color: #0000ff;">Enter configuration commands, one per line.  End with CNTL/Z.</span></p>]]></description></item><item><title>IOS XR – Basic MPLS and LDP (LDP Auth, OSPF, and ISIS)</title><link>https://hugo.fryguy.net/2012/10/01/ios-xr-basic-mpls-and-ldp-ldp-auth-ospf-and-isis/</link><pubDate>Mon, 01 Oct 2012 12:37:52 +0000</pubDate><author>Fryguy</author><guid>https://hugo.fryguy.net/2012/10/01/ios-xr-basic-mpls-and-ldp-ldp-auth-ospf-and-isis/</guid><description><![CDATA[<p><a href="/wp-content/uploads/2012/09/iosxrfryguy-8.jpg" rel=""></a><br>
Ok, time for some MPLS!  For this lab I will be using the OSPF routing protocol first, then we can move to IS-IS next.  All we will be doing here is configuring LDP<br>
First up, lets enabled LDP on all OSPF interfaces.  Normally you would do this under each interface, but here we will use the MPLS LDP AUTOCONFIG command.  This is a good command to use as it ensures that you do not miss configuring LDP on an interface.<br>
<span style="color: #0000ff;">RP/0/7/CPU0:R1#<span style="color: #ff0000;">conf t</span></span><br>
<span style="color: #0000ff;">Sun Apr  1 18:58:04.084 UTC</span><br>
<span style="color: #0000ff;">RP/0/7/CPU0:R1(config)#<span style="color: #ff0000;">router ospf LAB</span></span><br>
Under the OSPF LAB process, we need to configure mpls ldp autoconfig and then commit it.<br>
<span style="color: #0000ff;">RP/0/7/CPU0:R1(config-ospf)#<span style="color: #ff0000;">mpls ldp auto</span></span><br>
<span style="color: #0000ff;">RP/0/7/CPU0:R1(config-ospf)#<span style="color: #ff0000;">commit</span></span><br>
<span style="color: #0000ff;">Sun Apr  1 18:58:12.277 UTC</span><br>
<span style="color: #0000ff;">RP/0/7/CPU0:R1(config-ospf)#<span style="color: #ff0000;">exit</span></span><br>
<span style="color: #0000ff;">RP/0/7/CPU0:R1(config)#exit</span><br>
Ok, now lets see what interfaces have LDP on them<br>
<span style="color: #0000ff;">RP/0/7/CPU0:R1#<span style="color: #ff0000;">sh mpls ldp int</span></span><br>
<span style="color: #0000ff;">Sun Apr  1 18:58:18.902 UTC</span><br>
<strong><span style="color: #0000ff;">MPLS LDP application must be enabled to use this command</span></strong></p>]]></description></item></channel></rss>