Resource Library

ITIL describes a service portfolio as a collection of the overall set of services managed by a service provider. A service portfolio describes a service provider’s boundaries and promises across all of the customers and market spaces it serves. I like to think of a service portfolio as describing the past, present, and future collection of services offered by a service provider. The figure below shows a high-level view of a service portfolio.

Depending on the switch vendor, the exact steps will vary on how to set up and configure VLANs on a switch. For the network design shown, the general process for setting up VLANs on the switch is:

We already covered the first three of the twelve advantages of Agile software development. These three advantages focus on team development and refining the process. Advantage #4: Motivated Development Team The positive relationship with a reasonable and satisfied customer is only one of the reasons why many developers prefer to work on Agile projects. The other main contributor is that they tend to value working in self directed teams (which the Agile methods require for success).

Now that the network is installed, each switch has a bridge ID number, and the root switch has been elected, the next step is for each switch to perform a calculation to determine the best link to the root switch. Each switch will do this by comparing the path cost for each link based on the speed. For paths that go through one or more other switches, the link costs are added. The switch compares this aggregate value to the other link costs to determine the best path to the root switch.

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.

Some of you might just be starting out as a database administrator and need to know what a basic Transact-SQL query is for Microsoft SQL Server 2012, others might already be creating database objects. Either way, we put together a list of a few terms regarding Microsoft SQL Server that any database administrator should know.

As we discussed previously, Cisco created the Nexus Operating System (NX-OS) to power its next-generation data-center switching platform. While this new OS shares many similarities to the original IOS, there are some definite differences that you need to be aware of as you begin using it.

Knowledge Management examines how we acquire, organize, manage, share, and utilize knowledge and information. The Internet gives us an overwhelming amount of information on a daily basis — and the volume of information available is growing rapidly! One of the biggest challenges for individuals and organizations involved in project management is to make the best use of this knowledge and information so they can operate more efficiently, improve decision making, and sustain a competitive advantage.

In the last two posts I discussed aspects of services in the context of some landscaping work that I’m having done. This is clearly what many people would call a “non-IT example.” I often use similar examples in my classes. However, I might initially describe an example that seems unrelated to IT, but will conclude with a challenge to students. That challenge is, “identify the IT in this example.” The truth of the matter is that most businesses these days are underpinned by some form of information technology. In fact, technology has become so ingrained into everyday services that often even the service providers themselves don’t realize how technology supports their business.

Lessons learned is a theory, or conclusion, based on evidence at a given time and describes what went wrong (as well as what went right) throughout the lifecycle of a project. Although it’s completed during the project closeout process, it should occur during the entire project lifecycle to ensure all information is captured and documented. Consequences of not having a project review of lessons learned are the increased likelihood of repeating actions that might have caused: