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:

Welcome to a new series of blog posts that I am working on.  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. 

Our first author for this series is Peter V Southwick whose latest book is Juniper Networks Warrior published by O’Reilly Press.

Author Name: Peter V Southwick

Book Title: Juniper Networks Warriors

Book Publisher: O’Reilly

Author Social Media Handle/Web Site/Public Contact: Linked-in: Peter V Southwick /peter@proteus.net

Other books authored: Juniper Enterprise Routing 2^nd ed. (O’Reilly); ISDN Systems and Services 3^rd ed. (MCGraw-Hill); Telecommunications A Beginners Guide (Osborne); Handbook of Local Area Networks (Auerbach); JNCIE-SP Workbook (Proteus Press)

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?

I’m a fourth generation telephone brat. My great-grandfather started the Champlain Telephone Company, which he passed through the generations. My brother and 1st cousin both still work for the company.

Time to do some IS-IS labs.  I am going to try and make these short and simple.  I am sure as I get more into Junos I will write more complex IS-IS topologies and start to include LDP as well.

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)

Let’s do RIP Authentication first. 

First, up – md5 authentication between R4 and J1 only.

For this exercise, we will use the password of JNPRCSCO for the link authentication between the routers.