Resource Library

If you want to stay relevant as an IT professional, you have two choices: evolve your current skills or make a big change.

Projects are a social endeavor. Traditional project management approaches have shied away from the social advantages a more agile project environment brings. By nature, we are storytelling, pattern seeking and social people. We need colocation to shine truly in a project environment.

Cisco Internetwork Operating System (IOS) has been around since a little after the inception of Cisco Systems as a company. In 1984, Len and Sandy Bosack from Stanford University founded Cisco Systems with a small commercial gateway server. The first Cisco router that I touched was an Advanced Gateway Server (AGS), which was the first marketed product of the company. After this came the Mid-Range Gateway Server (MGS), the Compact Gateway Server (CGS) and later the Integrated Gateway Server (IGS) and AGS+. The first version of IOS that I touched was 8.2(7). The operating system was based on a Unix-based system and was designed as a monolithic operating system, meaning that processes are stacked and interrelated.

A strong event management process that is able to detect changes of state throughout an organization’s IT environment is a key aspect of a complete suite of service management processes. Event management ultimately helps an organization maintain control through an understanding of the state of things, and how the state of those things changes in an IT environment.

Event management, although theoretically different, is fundamentally what most IT organizations refer to as “monitoring.” Monitoring an organization’s environment to determine whether important assets are in the state they should be, and knowing when that state changes, is a very important activity that many organizations spend significant portions of their budget doing.

Accessing cloud-based resources, whether they be IaaS/PaaS/SaaS-based, is very convenient. With a browser and Internet connection, you are up and running. No driving to your work office, no need to log into the corporate network. Just open up your web browser and go. This convenience, however, comes with a security risk. All of your business work is conducted over an insecure communication network. Unlike your office network, where the network link between you and the data center is under corporate control and is physically secure, the cloud access link is over the Internet.

Young adults unable to find work, employers unable to fill jobs, a recent GAO study that reported substantial declines in telecommunication expertise — there has been a lot of news about the pervasiveness of skills gaps, their causes, the actual impacts and what to do about them. It’s rather confusing, because the term “skills gaps” has been hijacked to politicize an extremely wide range of issues.

Most organizations quickly realize that knowledge management must be integrated with incident management in order to improve the quality of service and the efficiency of providing assisted service. What is not as quickly recognized is the value of integrating knowledge management with problem management.

UFFA, which stands for “Use it, Flag it or Fix it, Add it,” is the responsibility of every support professional in the knowledge management process. It comes from the Knowledge-Centered Support (KCS) methodology where knowledge management is based on collaboration and a shared ownership of the knowledge base. Let’s break it down.

That depends on their configurations. For example: While it makes very good sense to include redundant physical links in a network, connecting switches in loops, without taking the appropriate measures, will cause havoc on a network. Without the correct measures, a switch floods broadcast frames out all of its ports, causing serious problems for the network devices. The main problem is a broadcast storm where broadcast frames are flooded through every switch until all available bandwidth is used and all network devices have more inbound frames than they can process.