Ok, this post is a bit out of the ordinary for me, but I wanted to pass along some information that was sent to me and post it as a “guest-post”.  I will be attending the ONS Summit next week as part of the company that I work for, Torrey Point – Full-Service Network Consultancy, as a paid participant.  I wanted to share this post with you in the case that you would be attending, perhaps we can meet up when time allows.

–  Fryguy

Software Defined Networking (SDN) is the buzzword on the mind of every player in the networking and telecom ecosystem; promises to revolutionize networking as we know it and will affect service provider networks, cloud networks and enterprise networks.

Open Networking Summit (ONS) 2013 is the premier conference for SDN and Open Flow and has established itself as the leading event to ‘plug-in’ to SDN. 

Well that image there might be familiar to some of us!  But good news, once again, the CCIE Labs will be available as Cisco Live 2013!

Below is an e-mail I just received, so if you are ready, no better place to take the lab then Cisco Live!

CCIE Lab Exams Available June 22-23 at Cisco Live 2013, Orlando

Attending Cisco Live in Orlando? You can take your CCIE lab exam while you are there.
We encourage you to take advantage of the CCIE lab exams that will be available in Orlando June 22-23 as part of Cisco Live. The CCIE labs being offered during the event will allow qualified candidates who are registered for Cisco Live to more easily and quickly take the exam, reducing the waiting time, effort, and costs accrued by having to travel separately. The eight-hour lab exam tests your ability to configure actual equipment and get the network running in a timed-test situation.

First we can start with changing it on R4:

R4(config)#router ospf 1

R4(config-router)#router-id 44.44.44.44

Reload or use “clear ip ospf process” command, for this to take effect

So we have to clear the OSPF process in order for this to take effect.

R4(config-router)#^Z

R4#clear ip ospf process 

Reset ALL OSPF processes? [no]: y

R4#

Ok, we should now have a Router-ID of 44.44.44.44.

R4#sh ip ospf  | inc ID 

 Routing Process “ospf 1” with ID 44.44.44.44

Good.  Time to recheck connectivity.

R4#ping 3.3.3.3 so lo 0

Type escape sequence to abort.

Sending 5, 100-byte ICMP Echos to 3.3.3.3, timeout is 2 seconds:

Packet sent with a source address of 4.4.4.4

!!!!!

Success rate is 100 percent (5/5), round-trip min/avg/max = 1/1/4 ms

R4#

Good, we can still ping R3 from R4.  Now, let’s do the same thing on J2.

Recently I purchased a Celstron 127SLT Telescope and also purchased what is called a T-Adapter for my Sony NEX 3 Camera. I was trying to figure out how to do Astrophotography with it –  and after some serious Internet searching, I was able to fine 1 line that said how to get the adapter to work with the camera.  Hopefully by publishing this post, I can save some search and frustration efforts for other people.

Here is a picture of the Celestron 127SLT telescope that I purchased.  I chose this one based on personal feedback from people I communicate with on Twitter as well as I felt thees options would help me actually USE this telescope:

• Maksutov-Cassegrain, which as I understand makes it more suitable for lunar and planetary viewing
• Fully Computerized so it would be easier to find planets / stars
• 127mm Aperture (5”)

Time to continue the Author Series of posts, this time with Ron Fuller, CCIE 5851.   It is the intention of these interviews to bring a human side to the technical author.  I feel that each author has a story to share , and I wanted to provide them a way to share that story.

Author Name: Ron Fuller

Book Title: NX-OS and Cisco Nexus Switching – Next-Generation Data Center Architectures 2^nd Edition

Book Publisher: CiscoPress

Author Social Media Handle/Web Site/Public Contact: @ccie5851 ccie5851.blogspot.com

Other books authored:

NX-OS and Cisco Nexus Switching – Next-Generation Data Center Architectures 1^st Edition

Building Cisco Wireless LANs

Cisco QoS

1.       Tell us a little background on yourself; is there anything unique about you that you would like to share that people might not be aware of?

It has come time for me to move my hosting to a local provider.  I now have a server hosted at a Data Center in Philadelphia, PA –  near my home.  I am still working out a few bugs with the new site, so if you see anything odd please feel free to contact me about it.  I have one post –  the latest Cisco Live one that is fighting me right now.

Well it is getting close to that time of year and we are just a little over 90 days away from the Cisco Live event – wow, can you believe it, where has time gone?!?!
In case you have missed it, I posted some information on the Keynote and the CAE a few months ago – you can read that post here: http://www.fryguy.net/2013/01/26/cisco-live-us-keynote-information/
Now let us get on with this post and some updates:
First up – Tom (@networkingnerd) has a Twitter List going again. Tom put it best by saying:

Well it is getting close to that time of year and we are just a little over 90 days away from the Cisco Live event – wow, can you believe it, where has time gone?!?!
In case you have missed it, I posted some information on the Keynote and the CAE a few months ago – you can read that post here: http://www.fryguy.net/2013/01/26/cisco-live-us-keynote-information/
Now let us get on with this post and some updates:
First up – Tom (@networkingnerd) has a Twitter List going again. Tom put it best by saying:

The Cisco Live Twitter List has been going strong for the last few years. This list exists for all the networkers using Twitter that would like to see who else is attending. Twitter is not only a great way to keep in touch outside of Cisco Live, but it serves a great function during the event. By following people that are attending, you can use Twitter to coordinate events, catch up after hours, and even use direct messages (DMs) to communicate when the local cellular network inevitably fails due to the influx of 20,000 extra people.

You can add yourself to the list by clicking on the NERD icon below:

[]2
Had a small problem today that was interesting, but not unique.  I have seen this problem before, but realized that maybe most people might not know how to fix it. I think the normal approach that people take is a reload of the device, not always a good thing to do on a production network in the middle of the day.
So the  depicts is a VTY session that is unclearable via the normal clear command route.  When you do a who, you see that someone is connected to VTY 0 for an extended period of time:

Switch1#who
    Line       User       Host(s)              Idle       Location
   1 vty 0                idle                     6w4d HackerHost.virtua.com.br
*  2 vty 1     jfry       idle                 00:00:00 192.168.0.1
  Interface      User        Mode                     Idle     Peer Address
Switch1#

They are not logged in as there is no User listed, but you can see they have been idle for 6 weeks and 4 days.
So the first think that you would do would be to clear the session and do a who again to make sure they are gone.

Switch1#clear line vty 0
[confirm]y [OK]
Switch1#who
    Line       User       Host(s)              Idle       Location
   1 vty 0                idle                     6w4d HackerHost.virtua.com.br
*  2 vty 1     jfry       idle                 00:00:00 192.168.0.1
  Interface      User        Mode                     Idle     Peer Address
Switch1#

Odd, they are still there.  Well, maybe its VTY 1 and not __, lets clear that one instead:

This post continues off the previous JUNOS posts.

Ok, time to rollback to the rescue configs. 

Up first replacing the config on R4  (if you have not done this in the last lab)

R4#configure replace flash:base.txt

Ok, that’s done – J1, J2, and J3 next.

First up, we need to roll-back to the rescue config. This is done from the edit mode by issuing the command rollback rescue.

jfry@J1> edit

Entering configuration mode

[edit]

jfry@J1# rollback rescue

load complete

[edit]

jfry@J1# commit and-quit

commit complete

Exiting configuration mode

jfry@J1>

Now to J2: