My experience leads me to think that information security is, in actual practice, more a matter of reacting to something bad that happened in the news shaking up the C-level enough to do something. But I don’t think the solemn promises of tighter security and subsequent actions match up. I may not be able to spot a tell like Patrick Jane, but something doesn’t seem right.
This post is a short, sweet and to the point copy/paste resource for configuring Cisco’s Virtual Switching System.
Being a good network engineer requires a strong technical skill set. In fact there’s an entire industry devoted to technical training in networking technologies. We know that persistent technical training is necessary to keep pace with constant changes in technology, so I’m sure we agree that technical proficiency is important for the network engineer. If you don’t have a deep understanding of how VPN technology works, you’ll have a very difficult time troubleshooting a site-to-site VPN without the help of some [unnamed] technical assistance center. But is that all that’s required for a successful career in networking?
Few fields require the continual professional development that IT does, but few fields offer the incredible rewards that a commitment to developing the skills of our trade can provide. Many factors come together to shape if, why, and how we advance in our field, and though I can speak only of my own experience, I believe the lessons I’ve learned from my journey so far may be of some value to others also on a similar path.
This week’s post will cover basic information gathering and configuration of Cisco Nexus switches. I’ll be using the 5500 series as my example and covering the basics without getting into features such as fibre channel, VSANs and that sort of thing.
A brief overview of Cisco Nexus switches.
I get pretty excited when new network gear shows up at the loading dock. I get psyched when I get to configure an interesting technology that I rarely get to use. But considering our responsibility to our customer or employer, sometimes we need to put that aside in favor of the simpler (or cheaper) but more appropriate solution. Let me give you one example.
How many times has one of your network projects come to a screeching halt (probably at 2am) because you didn’t have the right power plug or patch connector? Seems like such a trivial thing, but millions of dollars of equipment won’t do much more than look pretty in the racks until it’s all powered up and connected together.