I love when tools make my life easier. A conversation came up online the other night and I had shown someone a quick summary of the awesome power of Sublime Text. They wanted to know how I made the magic happen in that video. I felt I should and share it with everyone via a blog post. Here’s a quick video of my uses along with a description of what you can do with it, as well as how to make it work.
Permanent link to this article: http://www.packetpilot.com/config-ease-with-sublime-text-snippets/
The other day someone joked that I should write a post about plugging in a cable, or at least something to that extent. Then I started thinking about it. It’s actually a good idea. Everyone has their own way of cabling up a rack of patch panels and switches. Most of us would love to get the exact right length cables for the job however, that’s often not the case. There is a patching strategy I like to use when you are stuck using a box of 7 foot cables when all you really need are 3 foot cables. None the less, we all want it to look as neat as it can when we are done. I’m going to show you my practice when it comes to patching which can be easily modified whether you’r racks follow a panel-switch-panel-switch arrangement or a panel-panel-switch-switch arrangement.
Permanent link to this article: http://www.packetpilot.com/back-to-basics-patching-a-switch/
I.T. has had a large past of using animals to describe individuals, their attitudes, their skill sets, etc. Some of these originated outside of Information Technology such as the age old “Paper Tiger”. We’ve used terms like coding monkey to describe a programmer capable of knocking out code repetitively and constantly.
I’m going to take a slightly different approach on this concept with a thought and philosophy I’ve been trying to get myself into the mindset of applying on a daily basis. This mindset is something we all have the chance to challenge ourselves on everyday in different situations. The concept is simple and the question goes like this. “Why not become the Raven, rather than the Macaw?” So what am I getting at here? It’s simple, we have two very different birds and many people will chose one or the other based on certain criteria. Here is my logic between the two.
Permanent link to this article: http://www.packetpilot.com/the-raven-or-the-macaw/
I had the circumstances of lack of budget, broken freeware, and understandable need put me in the position of spinning up another unsupported freeware application in the form of a UCCX Call Center Wallboard. As usual, I tend to be a gluten for punishment and tend to try and fight these type of situations into submission. Luckily for me in this case, I had a great solution (UC Guerrilla’s take on the free wallboard), as well as a great resource at my disposal. That resource is none other than one of the best Exchange, Server, and Client engineers I know, and am rather happy to call a friend and colleague; none other than ibageek03 on Twitter.
Permanent link to this article: http://www.packetpilot.com/uc-guerrilla-wallboard-on-server-2012-64bit/
A colleague and I have been debating over a few months the topic of troubleshooting. My initial stance on the topic was that you CAN teach troubleshooting. However, as time has passed working with particular individuals I have came to a realization that you CANNOT teach troubleshooting. My belief now is that some people simply have a mind that thinks in logical sequences to rule out options and others don’t. While I’m sure this post may cause some heat towards myself the point isn’t to say anything bad about anyone. My point is that some individuals have a very effective troubleshooting skill set, while others simply have a set rubric of tests that if exhausted, results in a complete halt in process. I’ve come up with four items that impact an individuals ability to troubleshoot effectively even after the initial checklist has been exhausted.
Permanent link to this article: http://www.packetpilot.com/you-coach-not-teach-troubleshooting/
I’ve been working on doing some multicast labs lately and am constantly resetting my lab devices to their default configs and starting from scratch. As many of us know, to enable PIM on all of your interfaces you must go into each interface and enable it manually. There is no default command to enable PIM on all interfaces. We know PIM should be enabled 1 to 1 with interfaces involved in routing making this a boon. With that in mind, and the fact that I am rather comfortable with the concept of needing PIM on the interfaces, and likely speak and type this command in my sleep, I decided to make it easier and modify a previous TCL script I had written to enable PIM on every interface that has an IP address assigned to it. With the great “Send to Chat” feature of SecureCRT I can do this across my entire topology on one fell swoop. In a real world environment, you could use a tool like Solarwinds to push this out to your devices.
Permanent link to this article: http://www.packetpilot.com/bulk-enable-pim-via-tcl/
The other night while studying I tweeted out the first six words that came to mind as I thought to myself “How can I retain this better”. The concept is really quite simple and I find myself doing these steps for everything I am trying to learn and retain. While everyone learns *best* a certain way, everyone also learns more by being around the material more. I don’t feel I need to explain how to find what way of learning works best for you. Nor am I going to pretend to have a clue how people learn or retain better in any sort of scientific way. I’m simply going to explain my view on my six word study method.
Read, watch, listen, learn, discuss, do!
It’s a simple mantra that you can think about every time you start studying a topic. In fact, you already learn all of these ways throughout the day. The concept here is to apply all six of them to every topic you are focused on studying.
Permanent link to this article: http://www.packetpilot.com/daily-learning-actions/
Windows for Network Engineers
Part two in my series of apps for network engineers across the three major platforms. I previously did the post for Mac when I first refreshed my laptop and purchased my first new Mac in 8 years. Issued by work, my daily laptop is a Windows machine which is fine with me. I would prefer to use Mac but give me a machine that has the tools I need and I’m fine. So with that in mind, I am going to list my favorite Windows tools for Network Engineers.
Permanent link to this article: http://www.packetpilot.com/apps-for-a-network-engineer-part-ii-windows/
Being the geek I am, I was troubleshooting an issue one day where I wanted to see what dial-peer a certain digit string was hitting on a gateway. I saw something that simply intrigued my mind that took focus away until I figured it out. This “thing” I saw was irrelevant to what I was troubleshooting but once the problem was resolved I simply had to figure it out. I’m sure many of you experience that same thing throughout your days. So, this is what I’ve discovered. *Please note that this is not an official explanation of the item/output, it is simply my interpretation from time spent figuring out what it really meant.
Permanent link to this article: http://www.packetpilot.com/what-is-that-timestamp-dial-peers-last-setupdisconnect-time/
[notice]For this example I use the following IP scheme 192.168.0.12|–O–126.96.36.199—–[INTERNET]——188.8.131.52–O–|10.42.42.42[/notice]
I was approached a few weeks back to assist in creating a VPN Tunnel between two end points. Of course in my naivety I readily assumed it was between to Cisco devices but that turned out not to be the case. The tunnel was to be between a Linux box (in this case Ubuntu on a hosted VPS provider) and an unknown endpoint. This tunnel was going to be host to host as opposed to LAN to LAN. After some quick discovery work, getting access to the Linux box, and seeing the required proposal from the other side I started diving into the unknown of Openswan. Luckily, after doing som research for the configuration and verification things started shaping up and much to my approval, a lot of what you would look for in Cisco verification was the same on the Linux box. The configuration goes as such.
Naturally the first step is to install Openswan. As per usual use your distributions software management to install this. The first thing I configured was the ipsec configuration file. On the Ubuntu box this resided in “/etc/ipsec.conf”. The configuration was as follows.
Permanent link to this article: http://www.packetpilot.com/linux-to-cisco-openswan-ipsec-configuration/